Closed
Bug 595283
Opened 14 years ago
Closed 12 years ago
3.6.9 browser crash when I lock/unlock terminal
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: lindus, Unassigned)
Details
(Keywords: crash, Whiteboard: [testday-20120413])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100824 Firefox/3.6.9 Since I updated to FF 3.6.9 the browser crashes as soon as I unlock my terminal after locking it. This happens consistently Reproducible: Always Steps to Reproduce: 1. Lock terminal 2. Login/Unlock terminal 3. Actual Results: Browser crashed Expected Results: Browser will continue to work as usual Win7 Ultimate FF 3.6.9
Comment 1•14 years ago
|
||
Please post a crash ID from about:crashes https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
Comment 2•14 years ago
|
||
Glad to see I'm not the only one having the problem. I'm only using the 32 bit version but it has been crashing alot in the past few days.
Reporter | ||
Comment 3•14 years ago
|
||
Here's the crash IDs I get when I do "about:crashes" in the URL bar: Report ID Date Submitted bp-601ad26f-5095-4e85-8c1f-175422100913 9/13/2010 4:21 PM 10c5f13c-a5e7-485d-9ca7-a7cf7ebca364 9/13/2010 12:46 PM 1ca7b0e0-7d17-4786-8b6e-e4b316e1a46e 9/13/2010 11:39 AM 50dafc3c-da46-473e-9795-c608bf3fa920 9/13/2010 10:27 AM a7a02e23-3f30-42b2-8928-190d40d5e03f 9/10/2010 6:43 PM 3f033606-f8e6-4505-944b-6d68cebe36c1 9/10/2010 12:18 PM 006f5458-cdad-46c5-87b6-d3cd5c920eba 9/10/2010 10:22 AM 701df55e-fdd8-4f20-897f-187df60f4df0 9/9/2010 6:30 PM With hopes this helps, /Johan
Comment 4•14 years ago
|
||
The reports without "bp-" in front need to be send to the crash server. Just click on the link for each report in about:crashes and post the new IDs. Doing that for 3 reports should be enough. The first ID with bp- seems to be broken and I hope that one of the other ones work.
Comment 5•14 years ago
|
||
Reporter, were you able to resubmit the crash reports?
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #5) > Reporter, were you able to resubmit the crash reports? I tried a number of times but as the situation made my usage untenable I downgraded to 3.6.8 and then upgraded to 3.6.10 If I can resubmit them I will. With hopes this helps /Johan
Reporter | ||
Comment 7•14 years ago
|
||
Ok, succeeded in submitting them: Report ID Date Submitted bp-8c2cf3c0-a33c-48ae-9a3b-d6ba82101025 10/25/2010 12:42 PM bp-a65bb454-a571-4c54-acc8-27c4c2101025 10/25/2010 12:41 PM bp-8555aab4-6e5e-48e2-9cb1-a1a5d2101025 10/25/2010 12:41 PM bp-6b5b718f-914d-42f7-9771-0eca82101025 10/25/2010 12:40 PM bp-2c3b4c1b-c953-4df5-82a2-3e4b62101025 10/25/2010 12:39 PM bp-a31967f4-5299-47ad-b8b3-bcc602101025 10/25/2010 12:32 PM With hopes this sheds some clarity, /Johan
Comment 9•14 years ago
|
||
I can't help you, you need to ask someone on the Socorro team.
Comment 10•12 years ago
|
||
cant reproduce on Firefox 11, 12b4,13 and 14 for support please ask question in https://support.mozilla.org/questions/newc
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [testday-20120413]
You need to log in
before you can comment on or make changes to this bug.
Description
•