Closed Bug 134361 Opened 23 years ago Closed 23 years ago

crash when save source view in JSD

Categories

(Core :: XPCOM, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 134070

People

(Reporter: ajschult784, Assigned: dougt)

References

()

Details

(Keywords: crash)

Attachments

(1 file)

with Linux build 20020328, I crash when saving source view with attachment 67608 [details]. It seems to be dependent on the Javascript being active while saving, as I don't crash on Bugzilla pages which have Javascript that is inactive during the save. The source view is properly saved to disk before it crashes. Saving profile data has the same effect. talkback ID TB4627039K and TB4626590W generated with http://www.globalserve.net/~brent/tech/beam/ regression occurred between 2002032006 and 2002032108
Attached file stacktrace
based on the stacktrace, this looks like a dupe of topcrash bug 119693. cc'ing pavlov
*** Bug 134377 has been marked as a duplicate of this bug. ***
Keywords: crash
current CVS now usually throws an assertion before crashing: Assertion failure: 0 == rv, at ptsynch.c:191 also, the top of the stacktrace is slightly different: #0 0x405a0ae1 in __kill () at __kill:-1 #1 0x402a676b in raise (sig=6) at signals.c:65 #2 0x405a2062 in abort () at ../sysdeps/generic/abort.c:88 #3 0x40262112 in PR_Assert () at prlog.c:510 #4 0x40273cd1 in PR_Lock (lock=0x89e773c) at ptsynch.c:191 #5 0x40274794 in PR_EnterMonitor (mon=0x89e7738) at ptsynch.c:514 #6 0x401bc944 in PL_ProcessPendingEvents (self=0x8996528) at plevent.c:530 over to NSPR (not XPCOM)...
Assignee: rginda → wtc
Component: JavaScript Debugger → NSPR
Product: Browser → NSPR
QA Contact: caillon → wtc
if the real problem is farther up the stack, then this isn't NSPR... feel free to kick it back to JSD or over to XPCOM if you think NSPR is doing its job.
oops. and reassign. also marking NEW.
Assignee: wtc → dougt
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: wtc → scc
Can you print the value of rv in the debugger? This bug may be a duplicate of bug 134070 that Brian Ryner reported.
bryner and I believe that this indeed is the dup wtc mentioned. *** This bug has been marked as a duplicate of 134070 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
the patch in bug 134070 does fix the crash. any comment on comment 6? it seems to be the change that caused the regression here, and maybe in bug 134070 also.
this is working now (with patch from 134070)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: