Closed Bug 127927 Opened 23 years ago Closed 22 years ago

assertion nsBasicEncoder not thread-safe in nsFSStringConversion

Categories

(Core :: XPCOM, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.1alpha

People

(Reporter: timeless, Assigned: dougt)

References

Details

(Keywords: assertion)

steps and stuff are in bug 127918. bug cc list picked based on bug 43591.

#2  0x2826021d in nsDebug::Assertion (aStr=0x287ebc20 "nsBasicEncoder not thread-safe",
    aExpr=0x282ce560 "owningThread == NS_CurrentThread()", aFile=0x282ce520 "/home/timeless/mozilla/xpcom/glue/nsDebug.cpp",
    aLine=528) at /home/timeless/mozilla/xpcom/glue/nsDebug.cpp:291
#3  0x2826093c in NS_CheckThreadSafe (owningThread=0x80d9780, msg=0x287ebc20 "nsBasicEncoder not thread-safe")
    at /home/timeless/mozilla/xpcom/glue/nsDebug.cpp:528
#4  0x287d7d95 in nsBasicEncoder::Release (this=0x80baf40) at /home/timeless/mozilla/intl/uconv/src/nsUCvMinSupport.cpp:382
#5  0x281ed2c9 in nsFSStringConversion::CleanUp () at /home/timeless/mozilla/xpcom/io/nsLocalFileUnicode.cpp:146
#6  0x281ed274 in NS_ShutdownLocalFileUnicode () at /home/timeless/mozilla/xpcom/io/nsLocalFileUnicode.cpp:86
#7  0x281ed004 in NS_ShutdownLocalFile () at /home/timeless/mozilla/xpcom/io/nsLocalFileCommon.cpp:58
#8  0x281a8d11 in NS_ShutdownXPCOM (servMgr=0x0) at /home/timeless/mozilla/xpcom/build/nsXPComInit.cpp:560
#9  0x0804d256 in main (argc=2, argv=0xbfbff810) at /home/timeless/mozilla/netwerk/test/TestProtocols.cpp:650
Keywords: assertion
what's the build here? I think we changed this stuff near the end of 0.9.8, not
sure if any of this is still valid.
cvs from the morning i filed it or very close to that.
Bug 100676 is not checked in yet for Unix so this may still be valid. When that
goes in, this won't be valid. Or, to put a brighter spin on things, will be
fixed :-)
Blocks: 101976
Target Milestone: --- → mozilla1.1
please reopen if this still occurs
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.