Closed
Bug 678710
Opened 13 years ago
Closed 13 years ago
Crash after adding certificate override
Categories
(Core :: Security: PSM, defect, P1)
Tracking
()
RESOLVED
DUPLICATE
of bug 678440
mozilla8
Tracking | Status | |
---|---|---|
firefox8 | --- | affected |
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
This bug was filed from the Socorro interface and is
report bp-63773e2a-4d7f-45c3-869a-bf5c72110813 .
=============================================================
Build Identifier:
http://hg.mozilla.org/mozilla-central/rev/f262c389193e
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0a1) Gecko/20110812 Firefox/8.0a1 ID:20110812030744
While I test Bug 678706, I encountered a crash
[Str]
1. Open "https://www.cacert.org"
2. When "Untrusted Connection Page" displayed,
Click "I Understand the Risks"
3. Click "Add Exception..."
4. Uncheck "Permanently store this exception"
5. Click "Confirm Security Exception"
[Actual]
Crash with a Crash report.
Comment 1•13 years ago
|
||
I reproduced this on Windows 7. This is probably caused by the fix for bug 674571. Apparently there is some difference between synchronous events and synchronous XPCOM proxy invocations that I don't know of yet. IIRC, I remember being told that a sync event would be *appended* to the event queue but an sync XPCOM proxy invocation would cause the event to be *prepended* to the event queue, but I could be remembering wrongly.
Keywords: regression
Updated•13 years ago
|
status-firefox8:
--- → affected
tracking-firefox8:
--- → ?
Updated•13 years ago
|
Component: General → Security: PSM
Priority: -- → P1
Product: Firefox → Core
QA Contact: general → psm
Target Milestone: --- → mozilla8
Updated•13 years ago
|
Crash Signature: [@ RtlDeleteCriticalSection] → [@ RtlDeleteCriticalSection]
[@ nsHttpConnection::EndIdleMonitoring()]
[@ nsHttpConnection::Close(unsigned int) ]
[@ nsHttpConnectionMgr::GetConnection(nsHttpConnectionMgr::nsConnectionEntry*, nsHttpTransaction*, int, nsHttpConnection**)]
Summary: crash RtlDeleteCriticalSection → Crash after adding certificate override
Updated•13 years ago
|
Crash Signature: [@ RtlDeleteCriticalSection]
[@ nsHttpConnection::EndIdleMonitoring()]
[@ nsHttpConnection::Close(unsigned int) ]
[@ nsHttpConnectionMgr::GetConnection(nsHttpConnectionMgr::nsConnectionEntry*, nsHttpTransaction*, int, nsHttpConnection**)] → [@ RtlDeleteCriticalSection]
Comment 4•13 years ago
|
||
The reporter of bug 678709 claims that crashes might occur more often if you reload: "Click Reload button --- repeats step6 after few minutes, if browser does not crash."
(In reply to Brian Smith (:bsmith) from comment #1)
> I reproduced this on Windows 7. This is probably caused by the fix for bug
> 674571. Apparently there is some difference between synchronous events and
> synchronous XPCOM proxy invocations that I don't know of yet. IIRC, I
> remember being told that a sync event would be *appended* to the event queue
> but an sync XPCOM proxy invocation would cause the event to be *prepended*
> to the event queue, but I could be remembering wrongly.
Yes, that is correct.
Comment 6•13 years ago
|
||
https://crash-stats.mozilla.com/report/list?signature=RtlDeleteCriticalSection spiked in the last few days on 8.
Updated•13 years ago
|
Crash Signature: [@ RtlDeleteCriticalSection] → [@ RtlDeleteCriticalSection]
[@ nsHttpConnection::Close(unsigned int)]
[@ nsHttpConnection::EndIdleMonitoring()]
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
tracking-firefox8:
? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•