Closed Bug 666999 Opened 14 years ago Closed 13 years ago

nsSSLThread::stoppedOrStopping returns wrong value when it does not have a reference to the SSL thread

Categories

(Core :: Security: PSM, defect)

defect
Not set
critical

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox5 - ---
firefox6 - ---
blocking2.0 --- .x+

People

(Reporter: briansmith, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #468736 +++ The code is: PRBool nsSSLThread::stoppedOrStopping() { if (!ssl_thread_singleton) return PR_FALSE; return ssl_thread_singleton->exitRequestedNoLock(); } and it should be: PRBool nsSSLThread::stoppedOrStopping() { if (!ssl_thread_singleton) return PR_TRUE; return ssl_thread_singleton->exitRequestedNoLock(); }
Fwiw i've tried this change and it doesn't fix bug #669050
nsSSLThread is no longer a thing after the patches for bug 674147 landed.
Status: NEW → RESOLVED
Closed: 13 years ago
Depends on: 674147
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.