Bug 742793

Summary:	firefox -> security more info causes system lockup
Product:	[Fedora] Fedora	Reporter:	leland.ray
Component:	firefox	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	gecko-bugs-nobody, stransky
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-14 15:17:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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).