Closed
Bug 549435
Opened 14 years ago
Closed 14 years ago
TEST-UNEXPECTED-FAIL | "deadlock" test failing because of "WARNING: XPCOM objects created/destroyed from static ctor/dtor: 'gActivityTLS != BAD_TLS_INDEX && NS_PTR_TO_INT32(PR_GetThreadPrivate(gActivityTLS)) == 0"
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jrmuizel, Assigned: cjones)
References
Details
Attachments
(1 file)
1.83 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267471584.1267479011.6430.gz#err0 Running Deadlock detector correctness tests... WARNING: XPCOM objects created/destroyed from static ctor/dtor: 'gActivityTLS != BAD_TLS_INDEX && NS_PTR_TO_INT32(PR_GetThreadPrivate(gActivityTLS)) == 0', file /builds/slave/mozilla-central-linux64-debug/build/xpcom/base/nsTraceRefcntImpl.cpp, line 974 TEST-PASS | Sanity TEST-PASS | Sanity2 TEST-PASS | Sanity3 TEST-PASS | Sanity4 TEST-PASS | TwoThreads (expected 0 == return code, got -1) (output) ---------------------------------- ---------------------------------- (error output) ---------------------------------- WARNING: XPCOM objects created/destroyed from static ctor/dtor: 'gActivityTLS != BAD_TLS_INDEX && NS_PTR_TO_INT32(PR_GetThreadPrivate(gActivityTLS)) == 0', file /builds/slave/mozilla-central-linux64-debug/build/xpcom/base/nsTraceRefcntImpl.cpp, line 974 ---------------------------------- NEXT ERROR TEST-UNEXPECTED-FAIL | deadlock WARNING: XPCOM objects created/destroyed from static ctor/dtor: 'gActivityTLS != BAD_TLS_INDEX && NS_PTR_TO_INT32(PR_GetThreadPrivate(gActivityTLS)) == 0', file /builds/slave/mozilla-central-linux64-debug/build/xpcom/base/nsTraceRefcntImpl.cpp, line 1031 Finished running Deadlock detector correctness tests. nsStringStats => mAllocCount: 440 => mReallocCount: 236 => mFreeCount: 440 => mShareCount: 392 => mAdoptCount: 2 => mAdoptFreeCount: 2
Updated•14 years ago
|
Assignee: nobody → jones.chris.g
Comment 1•14 years ago
|
||
Yesterday's was the first I'd seen: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267352196.1267354089.20866.gz Linux x86-64 mozilla-central leak test build on 2010/02/28 02:16:36 s: moz2-linux64-slave06
Assignee | ||
Comment 2•14 years ago
|
||
What's actually going on here is something is being created/destroyed from a static context, the error message goes to stderr, and this test fails because it doesn't expect any output on stderr.
Assignee | ||
Updated•14 years ago
|
Summary: TEST-UNEXPECTED-FAIL | deadlock when doing Deadlock detector correctness tests → TEST-UNEXPECTED-FAIL | "deadlock" test failing because of "WARNING: XPCOM objects created/destroyed from static ctor/dtor: 'gActivityTLS != BAD_TLS_INDEX && NS_PTR_TO_INT32(PR_GetThreadPrivate(gActivityTLS)) == 0"
Assignee | ||
Comment 3•14 years ago
|
||
Attachment #429643 -
Flags: review?(benjamin)
Comment 4•14 years ago
|
||
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267563968.1267565641.13171.gz Linux x86-64 mozilla-central leak test build on 2010/03/02 13:06:08 s: moz2-linux64-slave04
OS: Mac OS X → Linux
Hardware: x86 → x86_64
Comment 5•14 years ago
|
||
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267660613.1267664239.27731.gz Linux x86-64 mozilla-central leak test build on 2010/03/03 15:56:53 s: moz2-linux64-slave07
Assignee | ||
Comment 6•14 years ago
|
||
bsmedberg, can this review be bumped up in your queue? It's a very small change. http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267678489.1267682413.16313.gz#err0 Linux x86-64 mozilla-central leak test build on 2010/03/03 20:54:49 s: moz2-linux64-slave04
Updated•14 years ago
|
Attachment #429643 -
Flags: review?(benjamin) → review+
Comment 7•14 years ago
|
||
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1267726053.1267728315.31419.gz Linux x86-64 mozilla-central leak test build on 2010/03/04 10:07:33 s: moz2-linux64-slave07
Assignee | ||
Comment 8•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/7e39e554e321
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•