Closed Bug 74962 Opened 25 years ago Closed 25 years ago

Crash in js_GC when closing mail compose window

Categories

(Core :: JavaScript Engine, defect)

PowerPC
Mac System 9.x
defect
Not set
blocker

Tracking

()

VERIFIED FIXED

People

(Reporter: beard, Assigned: shaver)

Details

Attachments

(1 file)

With latest JS engine changes (pulled at 2pm on 4/5/2001), I'm seeing a 100% repeatable crash in the JS GC. If I pull the following list of files using a 4/1/ 2001 date stamp, the crash goes away. Mind you, this is running on top of the Boehm GC, so if any changes have gone in that do any explicit pointer hiding, this can be the culprit, but I don't see any leaks that would point to that. Here's the list of files that appeared to have changed in my most recent pull: mozilla/js/src/jsxdrapi.c mozilla/js/src/jsobj.c mozilla/js/src/jsobj.h mozilla/js/src/jsprvtd.h mozilla/js/src/jspubtd.h mozilla/js/src/jsgc.c mozilla/js/src/jsgc.h mozilla/js/src/jsinterp.c mozilla/js/src/jslock.c mozilla/js/src/jslock.h mozilla/js/src/jsapi.c mozilla/js/src/jsapi.h mozilla/js/src/jscntxt.h mozilla/js/src/jsfun.c mozilla/js/src/js.c mozilla/js/src/js.msg
Attached file Stack crawl of crash
Update your js/src/liveconnect and rebuild -- that may fix it, although your stack doesn't show the top frames I'd expect. /be
Using my debugger, I determined that the crash is occurring on line 1216 of jsgc.c; evidently the finalizer that is getting called is garbage.
That's a static array element, referring to a C function. What can go wrong? Anyway to test that boehm isn't involved? /be
Yup, that fixed it. Closing bug.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking Verfied -
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: