Bug 742793 - firefox -> security more info causes system lockup
Summary: firefox -> security more info causes system lockup
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-02 20:30 UTC by leland.ray
Modified: 2012-02-14 15:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 15:17:46 UTC
Type: ---


Attachments (Terms of Use)

Description leland.ray 2011-10-02 20:30:50 UTC
Description of problem:

Running Fedora 15, current on updates.

In Firefox, navigate to any https page, click just to left of https to bring up security info.

Security summary dialog then appears "you are xxxx, verified by yyyy". Lower right hand corner button says "More information"

Clicking this button causes system lockup

* Running top shows firefox climbs to 100% of cpu
* X / gnome3 no longer accepts events, not possible to bring up any other window to check stack trace or get any additional information.
* Only way to bring back system has been to power down
* Happens for both verified and self signed certificates
* Running the 64 bit version

Version-Release number of selected component (if applicable):

firefox-7.0-1.fc15.x86_64

How reproducible:

always

Steps to Reproduce:

1. navigate to any https page
2. bring up certificate summary
3. click more information
  
Actual results:

Total system lockup. X no longer accepts any events, changing windows impossible.

Expected results:

Display of certificate

Additional info:

I've tried a few things to try and isolate the problem further. Rebooting to an older kernel does not affect the problem. /var/log/messages does not show any message that indicates a problematic component.

Not sure how to troubleshoot further, when this occurs my system is effectively dead.

Comment 1 Martin Stransky 2011-12-12 15:02:54 UTC
When it happens can you attach gdb to it? Find the firefox pid and attach debugger by:

$gdb --pid=xxx where xxx is the pid. 

Don't forget to install debuginfo packages by:

#debuginfo-install firefox xulrunner

when the gdb is attached, please list the backtrace here. (by "thread apply all bt" gdb commnad).


Note You need to log in before you can comment on or make changes to this bug.