There is a root level process which at least involves the write_store and lsregister files (part of the LaunchServices.framework) showing up as unknown user or even “Zombie” (?) processes. Can’t be killed as usual admin user.

This may not be related to LW, but last week trying 2.9.0 I noticed unknown and oddly named (symbol font?) by user “???” processes triggering Console entries like “ Process Viewer[406] enumerateProcessesAndFetch couldn't scan time.” Tried as root user today to isolate it/them and now know it’s independent of LW and an internet connection. One such process led to a link with the write_store & lsregister files

After usual maintenance, including root user completely uninstalling any p2p stuff, replacing the write_store, LSRecentTool & lsregister files from the original OS 10.2 CD, deep cleaning caches by JCC (long overdue), I’ve only since seen one more ??? process.

The original CD write _store file does includes something about a corrupt write/time:

dyld_mod_term_funcs __dyld_make_delayed_module_initializer_calls The kernel support for the dynamic linker is not present to run this program.
usage: store_write <store-name> <path>
d_corrupt .24s : Wrote corrupt store file %.4096s
/var/tmp/csstore.log

Don’t know that it affects LW, but hope this saves someone troubleshooting time.