A-NO-NE Music ([EMAIL PROTECTED]) on Thu, Nov 11, 2004 15:24 said: >I removed heap check then reboot, started PM5.1b3. Within 30 minutes,
You started PM with 'open' in Terminal, right? Did you see something like this when it started launching: malloc[371]: protecting edges malloc[371]: recording stacks using standard recorder malloc[371]: enabling scribbling to detect mods to free blocks >Meanwhile, the console log shows malloc memory stack error. No idea what >that means, but it doesn't sound good. My vm at this point is just 2, Could you copy and paste the error here? It probably means that PM has a memory-management related bug. >plenty of RAM left on my TiBook800/1GB, and boot volume has 3+GB free What OS are you using? >Another 20 minutes, the same thing happened again. It seems malloc is >making PM5.1b3 extremely unstable. More likely that PM is doing something wrong. >Since I didn't know how to stop malloc debugger, I rebooted at this >point. PM5.1b3 has not crashed since. You can't disable it once its launched. To run without it, just launch it from the Finder instead of from terminal. Is there a pattern to when it crashes? Are you typing? checking mail? switching folders? -- Erroneous google translation: "She does not love pig-turkey, the toys which make noise and especially the sound of the harmonica..."
