12 Dec 2014, 00:56
Today I uninstalled FinderPop 2.5.7 following the proper steps detailed in the application's Help. I'm on 10.6.8 and had installed only for one user (I didn't know FinderPop works properly only if installed for all users). Now every time I open System Preferences I get the Console message
kernel System Preferenc (map: 0xa4a6290) triggered DYLD shared region unnest for map: 0xa4a6290, region 0x7fff89000000->0x7fff89200000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
I have restarted more than once but this message sticks (and only for System Preferences). Searched with EasyFind and there seems to be nothing left behind after uninstallation, at least nothing whose name contains finderpop. I'm wondering what's going on. TIA.
12 Dec 2014, 15:09
Just tried uninstalling 2.5.7 on 10.9, and it works as expected, with no dyld shared unnest messages appearing after I rebooted.
The dyld shared unnest thing could be triggered by another "enchancer" that you may have installed... SIMBL plugins? Default Folder?
12 Dec 2014, 15:22
Thanks for replying. No, I've no other enhancer installed and never had dyld shared unnest messages before installing FinderPop (I take a look at Console on a fairly regular basis). What's puzzling is that I'm only getting the message on launching System Preferences.
Edit: I have XtraFinder installed, but it did never elicit such messages.
13 Dec 2014, 14:35
That dyld shared unnest message is generally caused by someone using the mach_override call - this can be done by third-party enhancers like FinderPop.
However If FP was uninstalled then it's a bit unlikely.
If you can run dtrace, see https://code.google.com/p/chromium/issu ... ?id=428858 for a great hint on how to catch who's doing this:
- Code:
$ cat > dyld-unnest.d
fbt::log_unnest_badness:entry {
printf("PID: %d", pid);
stack();
ustack();
}
$ sudo dtrace -s ./dyld-unnest.d
then open up System Preferences, the above will show you who's calling log_unnest_badness () which is the dyld routine that prints the shared-unnest complaint to the console log.
Failing that, can you send me your full console log? There may be a clue there. turly@finderpop.com
13 Dec 2014, 17:26
Thanks a lot. Unfortunately I think I'm too dumb for dtracing. The commands you suggested did create a file named dyld-unnest.d, but then nothing happened on launching System Preferences (actually I wasn't requested my administrator password after sudo). As far as I can understand, Instruments.app can work as a GUI for this, but I'm no expert. I'm mailing you my console log. Thanks again
13 Dec 2014, 23:40
(mdewakanton and I have taken this offline)