Jump to content

Google Chrome Helper triggered DYLD shared region unnest for map


tjdracz
 Share

4 posts in this topic

Recommended Posts

Hi all

 

Going through my console log I've noticed the log spam from Google Chrome Helper:

 

 

20/12/2014 14:29:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5ce10) triggered DYLD shared region unnest for map: 0xffffff8020b5ce10, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:30:22.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f1e0) triggered DYLD shared region unnest for map: 0xffffff8029f0f1e0, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:31:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cc30) triggered DYLD shared region unnest for map: 0xffffff8020b5cc30, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:31:29.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5ce10) triggered DYLD shared region unnest for map: 0xffffff8020b5ce10, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:31:31.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cd20) triggered DYLD shared region unnest for map: 0xffffff8020b5cd20, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:32:14.808 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.

20/12/2014 14:32:15.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f2d0) triggered DYLD shared region unnest for map: 0xffffff8029f0f2d0, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:32:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cc30) triggered DYLD shared region unnest for map: 0xffffff8020b5cc30, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:32:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cf00) triggered DYLD shared region unnest for map: 0xffffff8020b5cf00, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:32:27.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f1e0) triggered DYLD shared region unnest for map: 0xffffff8029f0f1e0, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:32:32.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f000) triggered DYLD shared region unnest for map: 0xffffff8029f0f000, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

20/12/2014 14:32:46.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cf00) triggered DYLD shared region unnest for map: 0xffffff8020b5cf00, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

 

As can be seen, the log errors are fairly regular and make the console log massive mess. Additionally, it seems like Google Chrome Helper is hogging my memory quite bad.

 

Anyone else had the same issue? Any suggestions?

 

Link to comment
Share on other sites

 

Hi all
 
Going through my console log I've noticed the log spam from Google Chrome Helper:
 
 
20/12/2014 14:29:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5ce10) triggered DYLD shared region unnest for map: 0xffffff8020b5ce10, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:30:22.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f1e0) triggered DYLD shared region unnest for map: 0xffffff8029f0f1e0, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:31:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cc30) triggered DYLD shared region unnest for map: 0xffffff8020b5cc30, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:31:29.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5ce10) triggered DYLD shared region unnest for map: 0xffffff8020b5ce10, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:31:31.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cd20) triggered DYLD shared region unnest for map: 0xffffff8020b5cd20, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:32:14.808 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
20/12/2014 14:32:15.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f2d0) triggered DYLD shared region unnest for map: 0xffffff8029f0f2d0, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:32:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cc30) triggered DYLD shared region unnest for map: 0xffffff8020b5cc30, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:32:22.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cf00) triggered DYLD shared region unnest for map: 0xffffff8020b5cf00, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:32:27.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f1e0) triggered DYLD shared region unnest for map: 0xffffff8029f0f1e0, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:32:32.000 kernel[0]: Google Chrome He (map: 0xffffff8029f0f000) triggered DYLD shared region unnest for map: 0xffffff8029f0f000, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
20/12/2014 14:32:46.000 kernel[0]: Google Chrome He (map: 0xffffff8020b5cf00) triggered DYLD shared region unnest for map: 0xffffff8020b5cf00, region 0x7fff8ea00000->0x7fff8ec00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
 
As can be seen, the log errors are fairly regular and make the console log massive mess. Additionally, it seems like Google Chrome Helper is hogging my memory quite bad.
 
Anyone else had the same issue? Any suggestions?

 

bump

Link to comment
Share on other sites

 Share

×
×
  • Create New...