Closed
Bug 302638
Opened 19 years ago
Closed 16 years ago
Sporadic crashes in background (Javascript-related?) [@ _releaseobject ]
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: neilio, Unassigned)
Details
Attachments
(1 file)
31.97 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050729 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b4) Gecko/20050729 Firefox/1.0+
I've already reported an earlier crash that I've been getting with the nightlies
(Bug #302355) and this is another one that I've seen quite often - about one
every two or three hours. The stack seems to be JS-related, also.
These crashes started occurring around the same time as Bug #302355's crashes
started (maybe about a week or so by now?).
The problem is I can't seem to find a consistently reproducible testcase. If I
can, I'll post an update.
Reproducible: Sometimes
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Oh, and this occurs with a brand new profile, too.
Reporter | ||
Comment 3•19 years ago
|
||
Arg. I shouldn't have entered "background" in the name of this bug - crashes
occur in the backgound as well as when Firefox is active. Sorry!
bug 293902 among others relates to crashing in js_FinalizeObject
actually both this and your bug 302355 are crashes under js_FinalizeObject, i'd
presume they're the same crash.
Assignee: nobody → general
Component: General → JavaScript Engine
Product: Firefox → Core
QA Contact: general → general
Summary: Sporadic crashes in background (Javascript-related?) → Sporadic crashes in background (Javascript-related?) [@ _releaseobject ]
Whiteboard: DUPEME
Version: unspecified → Trunk
Comment 5•19 years ago
|
||
Neil, are you still seeing this crash? Do you have any talkback incident ids?
Flags: testcase-
Reporter | ||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•