Closed Bug 93458 Opened 24 years ago Closed 24 years ago

EXC_BAD_ACCESS @ nsMacMemoryCushion::RecoverMemoryReserve(long) - heap corruption

Categories

(SeaMonkey :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 124517

People

(Reporter: hsivonen, Assigned: dcone)

Details

(Keywords: crash)

Attachments

(3 files)

Build ID: 2001080105 trunk FizzillaCFM I was using Bugzilla when Mozilla crashed. I can't give useful steps to reproduce. The crash.log excerpt (coming up) is all I've got.
Attached file crash.log excerpt
Keywords: crash
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
This is a duplicate I am sure of the content going away bug. 90060. Next time you submit a bug, a URL is really needed.. or a test case, its very hard if not impossible to fix a stack trace. I am guessing this is that bug because it looks like it was in the timer.. and I have a fix going in for that.. which crashes sites that content is changed.. dynamically or because the user switched pages, etc, etc. *** This bug has been marked as a duplicate of 90060 ***
Henri this should be fixed now...please try again..
Status: RESOLVED → VERIFIED
This is still the most frequent crasher I'm experiencing. I still don't have any useful steps to reproduce. It just happes upon a mouse click sometimes.
Crashed again. The stack is always the same. This time it was at http://www.appmac.com/, but I can't reproduce the crash when I try. I'm sure it'll reoccur when I'm not trying. I'll try to come up with steps to reproduce.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Summary: EXC_BAD_ACCESS @ RecoverMemoryReserve__18nsMacMemoryCushionFl () → EXC_BAD_ACCESS @ nsMacMemoryCushion::RecoverMemoryReserve(long)
I loaded http://lxr.mozilla.org/seamonkey/source/expat/xmlparse/xmlparse.c#117 Then I selected "m_externalEntityRefHandler" on line 381. Mozilla crashed when I pressed command-C. It doesn't crash if I do the same again. However, from time to time, Mozilla crashes with the same stack when handling some user event (mouse click or keyboard event). I believe the crash happens when the memory is in a particular state and that state can't be recreated by just redoing the last steps. Sorry, I can't come up with specific steps to reproduce. This happens seemingly at random when Mozilla has been in use for a long time. I open and close a lot of windows. I leave Mozilla open when I put the system to sleep at night. Mozilla has crashed 15 times on my computer in the 2001-10-29...2001-11-23 timeframe. Of those 15 crashes, 8 have been instances of this problem. CCing sfraser, because the CVS logs tell me he has worked on the related code.
Something is trashing the heap.
Summary: EXC_BAD_ACCESS @ nsMacMemoryCushion::RecoverMemoryReserve(long) → EXC_BAD_ACCESS @ nsMacMemoryCushion::RecoverMemoryReserve(long) - heap corruption
Attached file Another Crash Log
From 2001112608 - I got this submitting a form at http://www.wahoocomputers.com/cgi-bin/store/commerce.cgi?product=lanster_case . I happened to also be seeing bug 108470 at the time I hit the submit button, so I don't know if it's related, and I can't reproduce at the moment.
FWIW, this bug also exists in the 0.9.4 branch.
You could have the mozilla launcher script setenv MallocScribble=1 and MallocCheckHeapStart=1 and run Mozilla from the command line to help debug this.
Is nsMacMemoryCushion a Classic mamory management thing? Is it needed on OS X at all?
The only abnormal debug printout I saw was: MallocCheckHeap: PASSED check at 484998001th operation MallocCheckHeap: PASSED check at 484999001th operation At szone_check counter=970000 MallocCheckHeap: PASSED check at 485000001th operation MallocCheckHeap: PASSED check at 485001001th operation Then later when the crash happened, there was no useful printouts: MallocCheckHeap: PASSED check at 486289001th operation MallocCheckHeap: PASSED check at 486290001th operation MallocCheckHeap: PASSED check at 486291001th operation Segmentation fault Is this bug on any crash radar? Should this be moved to a more specific Bugzilla component?
Adding nominations. On my computer, this bug is a very frequent crasher and almost the only crasher.
simon, do you think this got fixed with your patch for the multiple-memcushions?
I checked in the fix for this yesterday. *** This bug has been marked as a duplicate of 124517 ***
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: