Closed Bug 348606 Opened 18 years ago Closed 18 years ago

Crash [@ _RtlEnterCriticalSection@4()] Debug only

Categories

(Core :: JavaScript Engine, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: bc, Unassigned)

References

Details

(Keywords: crash, regression)

Crash Data

beginning with 20060811 I began seeing crashes such as bug 341815 comment 15 on the trunk windows debug builds in browser tests in (at least) js1_7/iterable/regress-341510.js js1_7/iterable/regress-341815.js js1_7/geniter/fibonacci-matrix-generator.js > ntdll.dll!_RtlEnterCriticalSection@4() + 0x90 bytes msvcr80d.dll!_lock_file(_iobuf * pf=0x00240000) Line 238 C msvcr80d.dll!fprintf(_iobuf * str=0x00240000, const char * format=0x00553bf0, ...) Line 63 + 0x9 bytes C js3250.dll!js_Interpret(JSContext * cx=0x039b8fd8, unsigned char * pc=0x03df30eb, long * result=0x0012dd8c) Line 6168 + 0x4f bytes C timeless, in bug 341815 comment 18, says this is due to two threads trying to printf at the same time. This is a pain for me trying to wade through the js test results on a daily basis... There should be a thread safe way of dumping these messages out without crashing.
I no longer see the crashes on 20060818 builds, I claim this was fixed by 348027.
Status: NEW → RESOLVED
Closed: 18 years ago
Depends on: 348027
Resolution: --- → FIXED
Flags: in-testsuite+
verified fixed 1.9 20060824 windows/mac*/linux
Status: RESOLVED → VERIFIED
Crash Signature: [@ _RtlEnterCriticalSection@4()]
You need to log in before you can comment on or make changes to this bug.