Jon's Posts

Jon's Posts[Home]

Who	What
Jon 09 Nov 2010, 15:01	Re: DYLD problem related to FP? Thanks, Turly, for the explanation. I suspected that it wasn't really a problem (otherwise you'd have fixed it by now!) Anyway, I am reassured:-) Spot on, by the way. The iMac is 64-bit and the MBP is 32. To RonaldPR: the messages are (I think) in the asl.log ... but I see them because I have the Console App set to show "all messages". Interestingly, I used to see the type of message you describe, but now I don't get them I just get these new ones about dyld - which Turly has now explained and I can sleep easy.
Jon 08 Nov 2010, 12:21	DYLD problem related to FP? After installing FP 2.3.0 I have started to see the following messages in my log : 08/11/2010 10:45:25 kernel Finder (map: 0x69585c4) triggered DYLD shared region unnest for map: 0x69585c4, region 0x7fff82800000->0x7fff82a00000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 08/11/2010 10:54:48 kernel Finder (map: 0x5e84ae4) triggered DYLD shared region unnest for map: 0x5e84ae4, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 08/11/2010 10:54:51 kernel Mail (map: 0xc7cc290) triggered DYLD shared region unnest for map: 0xc7cc290, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 08/11/2010 10:54:53 kernel Console (map: 0x5969cd0) triggered DYLD shared region unnest for map: 0x5969cd0, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 08/11/2010 10:56:39 kernel Safari (map: 0x5e84000) triggered DYLD shared region unnest for map: 0x5e84000, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 08/11/2010 11:06:22 kernel TextEdit (map: 0xc7cc47c) triggered DYLD shared region unnest for map: 0xc7cc47c, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits. These messages occur for each Application I launch. The above is a sample. If I turn FP off then the messages do not appear, so it looks like FP is causing them. 1. Should I be concerned? 2. Is this a known side-effect of the current FP version? Intel iMac (2.66 GHz Core 2 Duo) running OSX 10.6.4 The problem does not occur on my MacBook Pro running the same OSX release. Many thanks for a great product which I have used for years.

Who

What

Jon
09 Nov 2010, 15:01

Re: DYLD problem related to FP?
Thanks, Turly, for the explanation. I suspected that it wasn't really a problem (otherwise you'd have fixed it by now!) Anyway, I am reassured:-)

Spot on, by the way. The iMac is 64-bit and the MBP is 32.

To RonaldPR: the messages are (I think) in the asl.log ... but I see them because I have the Console App set to show "all messages". Interestingly, I used to see the type of message you describe, but now I don't get them I just get these new ones about dyld - which Turly has now explained and I can sleep easy.

Jon
08 Nov 2010, 12:21

DYLD problem related to FP?
After installing FP 2.3.0 I have started to see the following messages in my log :

08/11/2010 10:45:25 kernel Finder (map: 0x69585c4) triggered DYLD shared region unnest for map: 0x69585c4, region 0x7fff82800000->0x7fff82a00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
08/11/2010 10:54:48 kernel Finder (map: 0x5e84ae4) triggered DYLD shared region unnest for map: 0x5e84ae4, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
08/11/2010 10:54:51 kernel Mail (map: 0xc7cc290) triggered DYLD shared region unnest for map: 0xc7cc290, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
08/11/2010 10:54:53 kernel Console (map: 0x5969cd0) triggered DYLD shared region unnest for map: 0x5969cd0, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
08/11/2010 10:56:39 kernel Safari (map: 0x5e84000) triggered DYLD shared region unnest for map: 0x5e84000, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
08/11/2010 11:06:22 kernel TextEdit (map: 0xc7cc47c) triggered DYLD shared region unnest for map: 0xc7cc47c, region 0x7fff88c00000->0x7fff88e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

These messages occur for each Application I launch. The above is a sample.

If I turn FP off then the messages do not appear, so it looks like FP is causing them.

1. Should I be concerned?

2. Is this a known side-effect of the current FP version?

Intel iMac (2.66 GHz Core 2 Duo) running OSX 10.6.4

The problem does not occur on my MacBook Pro running the same OSX release.

Many thanks for a great product which I have used for years.