Closed Bug 1341317 Opened 3 years ago Closed 3 years ago

Assertion failure: stack_[*size_].script() == script, at js/src/vm/GeckoProfiler.cpp:228 with enableGeckoProfiling and evalInCooperativeThread


(Core :: JavaScript Engine, defect, critical)

Not set



Tracking Status
firefox51 --- unaffected
firefox52 --- unaffected
firefox53 --- unaffected
firefox54 --- fixed


(Reporter: decoder, Assigned: bhackett)


(Blocks 1 open bug)


(4 keywords, Whiteboard: [jsbugmon:update])


(1 file)

The following testcase crashes on mozilla-central revision d84beb192e57 (build with --enable-posix-nspr-emulation --enable-valgrind --enable-gczeal --disable-tests --enable-stdcxx-compat --disable-profiling --enable-debug --enable-optimize, run with --fuzzing-safe):

  setInterruptCallback(function() { 


 received signal SIGSEGV, Segmentation fault.
0x0000000000b12c88 in js::GeckoProfiler::exit (this=0x7ffff695e230, script=0x7ffff078f1a8, maybeFun=<optimized out>) at js/src/vm/GeckoProfiler.cpp:228
#0  0x0000000000b12c88 in js::GeckoProfiler::exit (this=0x7ffff695e230, script=0x7ffff078f1a8, maybeFun=<optimized out>) at js/src/vm/GeckoProfiler.cpp:228
#1  0x0000000000bb8b0c in js::probes::ExitScript (popProfilerFrame=true, maybeFun=<optimized out>, script=<optimized out>, cx=0x7ffff6921000) at js/src/vm/Probes-inl.h:62
#2  js::InterpreterFrame::epilogue (this=0x7ffff02330b0, cx=0x7ffff6921000, pc=0x7ffff0311533 "\231\220Ә\a\210\003") at js/src/vm/Stack.cpp:269
#3  0x000000000052d443 in Interpret (cx=0x7ffff6921000, state=...) at js/src/vm/Interpreter.cpp:4235
#4  0x0000000000533232 in js::RunScript (cx=cx@entry=0x7ffff6921000, state=...) at js/src/vm/Interpreter.cpp:409
#5  0x0000000000535ce1 in js::ExecuteKernel (cx=cx@entry=0x7ffff6921000, script=..., script@entry=..., envChainArg=..., newTargetValue=..., evalInFrame=..., evalInFrame@entry=..., result=result@entry=0x7ffff0233090) at js/src/vm/Interpreter.cpp:690
#6  0x00000000005360a8 in js::Execute (cx=cx@entry=0x7ffff6921000, script=script@entry=..., envChainArg=..., rval=rval@entry=0x7ffff0233090) at js/src/vm/Interpreter.cpp:723
#7  0x00000000008c79ba in ExecuteScript (cx=cx@entry=0x7ffff6921000, scope=scope@entry=..., script=script@entry=..., rval=rval@entry=0x7ffff0233090) at js/src/jsapi.cpp:4475
#8  0x00000000008d8888 in JS_ExecuteScript (cx=cx@entry=0x7ffff6921000, scriptArg=scriptArg@entry=..., rval=...) at js/src/jsapi.cpp:4501
#9  0x00000000004581eb in Evaluate (cx=0x7ffff6921000, argc=<optimized out>, vp=<optimized out>) at js/src/shell/js.cpp:1812
#10 0x00000000005387ca in js::CallJSNative (cx=cx@entry=0x7ffff6921000, native=0x457d20 <Evaluate(JSContext*, unsigned int, JS::Value*)>, args=...) at js/src/jscntxtinlines.h:281
#23 0x0000000000438fee in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at js/src/shell/js.cpp:8320
rax	0x0	0
rbx	0x7ffff695e230	140737330405936
rcx	0x7ffff6c28a2d	140737333332525
rdx	0x0	0
rsi	0x7ffff6ef7770	140737336276848
rdi	0x7ffff6ef6540	140737336272192
rbp	0x7fffffffbca0	140737488338080
rsp	0x7fffffffbc70	140737488338032
r8	0x7ffff6ef7770	140737336276848
r9	0x7ffff7fe4740	140737354024768
r10	0x58	88
r11	0x7ffff6b9f750	140737332770640
r12	0x0	0
r13	0x7ffff078f1a8	140737227846056
r14	0x7ffff69201c0	140737330151872
r15	0x7ffff0311533	140737223136563
rip	0xb12c88 <js::GeckoProfiler::exit(JSScript*, JSFunction*)+648>
=> 0xb12c88 <js::GeckoProfiler::exit(JSScript*, JSFunction*)+648>:	movl   $0x0,0x0
   0xb12c93 <js::GeckoProfiler::exit(JSScript*, JSFunction*)+659>:	ud2
Whiteboard: [jsbugmon:update,bisect] → [jsbugmon:update]
JSBugMon: Bisection requested, result:
autoBisect shows this is probably related to the following changeset:

The first bad revision is:
user:        Brian Hackett
date:        Fri Feb 17 05:13:11 2017 -0700
summary:     Bug 1337968 - Add API and shell harness for cooperative multithreading, r=jandem.

This iteration took 0.479 seconds to run.
Brian, is bug 1337968 a likely regressor?
Blocks: 1337968
Flags: needinfo?(bhackett1024)
Attached patch patchSplinter Review
The Gecko profiler has a stack of profile entries, whose consistency can't really be maintained easily in a cooperatively multithreaded runtime.  This patch makes sure that the runtime is single threaded while the profiler is enabled, using the machinery added in bug 1341321.  Eventually it would be really good I think for the profiler to support multithreaded execution, but doing that might require pretty substantial changes inside and outside spidermonkey.
Assignee: nobody → bhackett1024
Flags: needinfo?(bhackett1024)
Attachment #8841226 - Flags: review?(shu)
Depends on: 1341321
Duplicate of this bug: 1342595
Comment on attachment 8841226 [details] [diff] [review]

Review of attachment 8841226 [details] [diff] [review]:

::: js/src/vm/GeckoProfiler.cpp
@@ +553,5 @@
>  JS_FRIEND_API(void)
>  js::EnableContextProfilingStack(JSContext* cx, bool enabled)
>  {
> +    if (!cx->runtime()->geckoProfiler().enable(enabled))
> +        MOZ_CRASH("Execution in this runtime should already be single threaded");

How is it ensured that the runtime should already be single threaded?
A related question: what kind of misuse results in enable(true) returning false? If the embedder's {Begin,End}SingleThreadedExecutionCallbacks are buggy?
(In reply to Shu-yu Guo [:shu] from comment #6)
> A related question: what kind of misuse results in enable(true) returning
> false? If the embedder's {Begin,End}SingleThreadedExecutionCallbacks are
> buggy?

This is not necessarily misuse, but normally when we force the embedding into single threaded mode the callback will need to yield while other threads finish whatever they are doing.  If during that process a second thread tries to enter single threaded mode then runtime->beginSingleThreadedExecution() will return false --- the first thread has dibs on being the one in single threaded mode, basically.

The MOZ_CRASH in EnableContextProfilingStack is kind of a placeholder --- right now the profiler code outside Spidermonkey doesn't handle multithreaded runtimes, so there's no way right now that we can hit this crash.  When the profiler does begin supporting multithreaded runtimes, there are a few options:

- This crash can be changed to a 'return false' and the failure bubbled up the call stack.  I looked into doing this for this patch but the calling profiler code is not so straightforward and it wasn't clear how it should fail in some cases.

- The calling code can interface with the Quantum DOM scheduling stuff to make sure that when it enables profiling it is always the only running cooperative thread, and doesn't need to worry about the beginSingleThreadedExecution() call failing.

- The profiler inside and outside Spidermonkey can be changed to handle multiple cooperative threads running at a time, and avoid the need to ensure the runtime is single threaded.

I don't know which of these options is best, so it seemed better to punt on handling this until work starts on supporting multithreaded runtimes from the Gecko side.
Attachment #8841226 - Flags: review?(shu) → review+
Pushed by
Require runtimes to be single threaded while the Gecko profiler is in use, r=shu.
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
Depends on: 1345262
You need to log in before you can comment on or make changes to this bug.