Closed
Bug 307370
Opened 19 years ago
Closed 17 years ago
PR_Cleanup does not wait all of the threads created in PR_Init
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 254987
People
(Reporter: m__p, Assigned: wtc)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; en) Opera 8.02 Build Identifier: nspr-4.4.1 The NSPR is statically linked with a dll. The crash happens after unloading the dll. It seems that PR_Cleanup does not wait all of the threads created in PR_Init. Reproducible: Always Steps to Reproduce: 1. Load the dll. 2. Call PR_Init. 3. Call PR_Cleanup and immediately unload the dll. 4. Wait... Actual Results: It crashes. Expected Results: I expect that PR_Cleanup will wait all of the threads, but it doesn't. It's general use case. I just initialize NSPR and then clean up it. Nothing more. Yes, there are some other threads in the process. But it's no matter. I hope so.
Comment 1•19 years ago
|
||
Actually, NSPR will "attach" to your other threads if you make any NSPR API calls within those threads. This means primarily that thread-private data is created, I believe. PR_Cleanup has many known limitations. See bugs 255452, 254983, 254987,
Updated•18 years ago
|
QA Contact: wtchang → nspr
Comment 2•17 years ago
|
||
This is a dupe of 254987 . The survival of the continuation and timer threads is what causes the crashes after the invocation of PR_Cleanup here.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•