Closed
Bug 1136384
Opened 9 years ago
Closed 9 years ago
Assertion failure: jsStackAddr != pseudoStackAddr && jsStackAddr != nativeStackAddr, at TableTicker.cpp:568
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1145333
People
(Reporter: mstange, Unassigned)
Details
Steps to reproduce: 1. Apply attachment 8568788 [details] [diff] [review]. 2. Build a debug build and run it like this: > MOZ_UPLOAD_DIR=~/Desktop/ mach crashtest gfx/tests/crashtests/815489.html The test crashes in the sampler thread with this stack: > Assertion failure: jsStackAddr != pseudoStackAddr && jsStackAddr != nativeStackAddr, at /Users/mstange/code/mozilla/tools/profiler/TableTicker.cpp:568 > #01: mergeStacksIntoProfile(ThreadProfile&, TickSample*, NativeStack&)[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x4385517] > #02: TableTicker::doNativeBacktrace(ThreadProfile&, TickSample*)[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x4384e24] > #03: TableTicker::InplaceTick(TickSample*)[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x4385a23] > #04: TableTicker::Tick(TickSample*)[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x438598a] > #05: SamplerThread::SampleContext(Sampler*, ThreadProfile*, bool)[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x4391a48] > #06: SamplerThread::Run()[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x4391811] > #07: ThreadEntry(void*)[/Users/mstange/code/obj-m-debug/dist/NightlyDebug.app/Contents/MacOS/XUL +0x438817e] > #08: _pthread_body[/usr/lib/system/libsystem_pthread.dylib +0x3268] > #09: _pthread_body[/usr/lib/system/libsystem_pthread.dylib +0x31e5]
Reporter | ||
Comment 1•9 years ago
|
||
Oh, and you need to build with ac_add_options --enable-profiling, otherwise you don't get C++ stackwalking.
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•