Closed Bug 724302 Opened 12 years ago Closed 12 years ago

Crash happens as I was doing a google search

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
10 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: britestarangie, Unassigned)

References

Details

(Keywords: crash) 

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0) Gecko/20100101 Firefox/10.0
Build ID: 20120129021758



Actual results:

The crash occured as I was doing a google search.
Can you reproduce this bug regularly or was this a one-time crash?  Do you have any other crash signatures from this issue that we can look at?

Crash Info: https://crash-stats.mozilla.com/report/index/a7995684-3918-460d-aed7-1c86b2120204
Signature: [@ EMPTY: no crashing thread identified; corrupt dump ]
Severity: normal → critical
Component: Mozbot → General
OS: All → Windows XP
Product: Webtools → Firefox
QA Contact: mozbot → general
Hardware: All → x86
Summary: bp-a7995684-3918-460d-aed7-1c86b2120204l crash happens as I was doing a google search. → Crash happens as I was doing a google search
Version: other → 10 Branch
It has happened a few times. How can Firefox prevent future crashes?
(In reply to britestarangie@aol.com from comment #2)
> It has happened a few times. How can Firefox prevent future crashes?

That depends on what exactly is causing this problem, and since the crash information is somewhat vague, we need more information about your installation of Firefox to determine a cause; seeing if the problem occurs in a fresh/new profile ( http://support.mozilla.org/en-US/kb/Managing-profiles#w_creating-a-profile ) will give us a lot of information as well.  Also, posting the exact steps to reproduce the bug will help us in testing and reproducing the problem.
Component: General → Untriaged
QA Contact: general → untriaged
Keywords: crash
I duped all the bugs to this one because they seem to be random crashes and all crash IDs results are empty/corrupt.

britestarangie@aol.com: Please open only new bug reports if the crash ID doesn't report a "corrupt dump". You should follow comment#7 and try a new profile first.
I was in google apps (not search) bp-9ba1646c-f708-454c-a123-e09592120211
(In reply to Wayne Mery (:wsmwk) from comment #17)
> I was in google apps (not search) bp-9ba1646c-f708-454c-a123-e09592120211
If you are able to reproduce it, please provide a stack trace (see https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report).
(In reply to Scoobidiver from comment #18)
> (In reply to Wayne Mery (:wsmwk) from comment #17)
> > I was in google apps (not search) bp-9ba1646c-f708-454c-a123-e09592120211
> If you are able to reproduce it, please provide a stack trace (see
> https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report).

Never reproduced -  I hadn't crashed before in the several times I've been to this gaps spreadsheet. SO I  mention it as an anecdotal datapoint - I'm not terribly interested in attaching my issue to britestarangie's ill defined crashes.
The empty signature doesn't allow to solve this issue.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
britestarangie@aol.com: For the moment we are resolving this as incomplete (as we don't have enough information to work on it further).  However, if you can give us more precise information about your profile, if this occurs in a new profile, and what the exact steps are to reproduce it, we will be able to reopen and address the problems you are seeing.
You need to log in before you can comment on or make changes to this bug.