| Summary: | Web Inspector: REGRESSION: JSC crashes when pausing at console.assert statement | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | BJ Burg <bburg> | ||||||
| Component: | JavaScriptCore | Assignee: | Saam Barati <saam> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Major | CC: | fpizlo, ggaren, joepeck, mark.lam, saam, timothy, webkit-bug-importer, ysuzuki | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | Mac | ||||||||
| OS: | OS X 10.10 | ||||||||
| Attachments: |
|
||||||||
|
Description
BJ Burg
2015-08-24 10:22:41 PDT
I can't seem to reproduce this using Spade-188767-74819. Possibly useful message that got dumped to console: toLength#CIvpti:[0x121ad8250->0x113499800, BaselineFunctionCall, 66 (StrictMode) (FTLFail)]: we have result = CompilationSuccessful but we are our own replacement. I was able to reproduce this with a build from Sunday, prior to ggaren's two patches being rolled back in. So this might be unrelated to those patches after all. Another one: readToken#AvwLUZ:[0x12822a250->0x119dc5f00, BaselineFunctionCall, 388 (StrictMode) (FTLFail)]: we have result = CompilationSuccessful but we are our own replacement. Created attachment 260288 [details]
better test case
Simpler steps to reproduce: STEPS TO REPRODUCE: 1. Open the attached test case. 2. Open Web Inspector 3. In Debugger tab, enable "Break on [All] Exceptions" (at the top of the left sidebar). 4. Set a breakpoint at the line with `console.assert(...)`. 5. Reload the inspected page. EXPECTED: * Should pause at at the breakpoint. Breakpoint should be hit before evaluating console.assert, which also pauses the debugger. ACTUAL: * Crashes with this callstack in Debugger::pause underneath evaluating console.assert. -- I have bisected the regression to this commit: http://trac.webkit.org/changeset/188714 Please advise whether this can be fixed quickly or it should be rolled out for further analysis. I still can't seem to reproduce this crash, using a debug or release build. Is there anything special to how you toggle breakpoints or reload the page? I can't promise a quick fix if I can't reproduce the crash -- but I also don't think the original patch will roll out cleanly :(. After a full rebuild on ToT, no longer able to reproduce. Closing for now. Saam was able to reproduce this last night on TOT. This no longer crashes for me |