524740 - crashed while playing a game on facebook

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Madison]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

crashed while playing a game on facebook

Reproducible: Sometimes

Steps to Reproduce:
1.15361125-0844-4fdb-a91b-6835d2091026
2.
3.
Actual Results:  
no clue how to do a reproduce

Comment 1

[Matthias Versen [:Matti]]

The stack looks useless for me :
Frame  	Module  	Signature [Expand]  	Source
0 	xul.dll 	xul.dll@0xa3ef3 	
1 	js3250.dll 	js_TraceObject 	js/src/jsobj.cpp:5805

Comment 2

[Madison]

(In reply to comment #1)
> The stack looks useless for me :
> Frame      Module      Signature [Expand]      Source
> 0     xul.dll     xul.dll@0xa3ef3     
> 1     js3250.dll     js_TraceObject     js/src/jsobj.cpp:5805

And that means what? I posted the three other crashes I received on the first report I made and was told they were all different. Then the other two are saying they are dups of the first one I made. You people are confusing me. Should I report things or not? I have no idea what I am looking for when it crashes. Just trying to report them. I am about to give up on firefox. It is getting frustrating!

Comment 3

[Wayne Mery (:wsmwk)]

Madison, are you still see this crash signature, or has it changed to what is seen in bug 523663?

Comment 4

[sean]

Is it better to mark this as a dup of 519886 based on the status of bug 524738?  Bug 524738 was marked as a dup of 519886 and this bug is the same problem.

Comment 5

[Matt Brubeck (:mbrubeck)]

(In reply to sean from comment #4)
> Is it better to mark this as a dup of 519886 based on the status of bug
> 524738?  Bug 524738 was marked as a dup of 519886 and this bug is the same
> problem.

Both bugs were reported by the same person, and both are crashes, but it's possible that the reporter of these bugs was affected by more than one bug.  The stack here looks different from the stack in bug 524738, so it's not necessarily the same underlying cause.

Comment 6

[sean]

In bug 523663 it shows the stack traces for both bug 524738 (comment 19 in 523663) and 524740 (comment 22 in 523663).  Maybe mark this and bug 524738 as a dup of 523663?

Comment 7

[Rachel Humphrey]

You guys make it sounds like we should know what all they codes mean. We get codes we send them all together if we got them all together. Your the professionals you tell us what goes with what and what they all mean. come on guys be professionals.

Comment 8

[Matt Brubeck (:mbrubeck)]

(In reply to Rachel Humphrey from comment #7)
> You guys make it sounds like we should know what all they codes mean.

Hi, sorry about that.  We appreciate you filing crash reports, and it's perfectly fine if you aren't familiar with the technical details.  We sometimes need to discuss the details among ourselves to make sure we get these bugs categorized right, but you can feel free to ignore those comments (or ask for clarification if you are interested).