Many lsbom processes from ODS 1.5.2
 

I just upgraded to ODS 1.5.2 on my Leopard (OS X 10.5) system. When I launch this, I get a bunch of lsbom processes started on my system. I don't even need to start scanning a drive. This starts as soon as the app is launched.

Eventually all my user processes are used up and I get errors stating "No more processes." when trying to run simple commands like "ls" under Terminal. Once I quit ODS, all these processes go away.

Here's a sample of what I see in Terminal when running "ps auxw | grep swaltner"...

[CODE]swaltner 2001 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 2000 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1999 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1998 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1997 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1996 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1995 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1994 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1993 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1992 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1991 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1990 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1989 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1988 0.0 0.0 0 0 ?? Z 2:31PM 0:00.00 (lsbom)
swaltner 1987 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1986 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1985 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1984 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1983 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1982 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1981 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1980 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1979 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1978 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1977 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1973 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1972 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)
swaltner 1971 0.0 0.0 0 0 ?? Z 2:30PM 0:00.00 (lsbom)[/CODE]

Apparently an Apple bug triggered by Corrupted BOM files
 

I've been talking with tech support at Omni Group and this looks like it's a bug in OS X that is triggered by corrupted .bom files in /Library/Receipts/. The developer thinks they can code around this in future releases of ODS. I've sent a copy of my Receipts folder to Omni Group so they have a copy of the .bom files that trigger this bug.

Steve