Sean McBride / 04.11.11 / 11:24AM wrote: >If its that slow, you can remove the last 2 lines... or change >MallocCheckHeapEach to something bigger like 100000. > >Its MallocScribble and MallocGuardEdges that find the most bugs in my >experience.
Plot thickens. I removed heap check then reboot, started PM5.1b3. Within 30 minutes, PM5.1b3 crashed, but no crash log was produced. Upon re-launching, PM went into that dreadful Rebuild Indices mode. Took 50 minutes to launch. 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, plenty of RAM left on my TiBook800/1GB, and boot volume has 3+GB free space. RAM sticks are known to be perfect condition since my work, DAW would crash at the far corner of mem addr while non other app crashes. Another 20 minutes, the same thing happened again. It seems malloc is making PM5.1b3 extremely unstable. Since I didn't know how to stop malloc debugger, I rebooted at this point. PM5.1b3 has not crashed since. Would this give any clue to my problem? I tried to take a look at malloc_history but it is a binary file. Do I need a special tool to view what's being logged? -- - Hiro [PROTECTED] <[PROTECTED]> <[PROTECTED]>
