Sean McBride / 04.11.11 / 0:26AM wrote: >export MallocStackLogging=1 >export MallocStackLoggingNoCompact=1 >export MallocScribble=1 >export MallocGuardEdges=1 >export MallocCheckHeapStart=1 >export MallocCheckHeapEach=1000
Thank you for the tip. I just tried it but it seems to be a little less practical since heap check is logging like crazy and my user proc is hitting the ceiling. Just switching out PM to desktop then back to PM took 3 minutes. Not to mention PM is action so slow. As I am typing this, I don't see what I am typing. I see the characters I typed a few lines before. Slow! ... Just now, I got 5 minutes spinning beachball while I was typing this... My suspicion to my ongoing PM crash goes to sort indices. Everything points to there in my observation. Assuming my prob is database specific (or even JP specific), and others are not having the problem, do you think I can kill heap check, or I should leave it on? -- - Hiro [PROTECTED] <[PROTECTED]> <[PROTECTED]>
