Closed Bug 1133781 (perf-tool-crashes) Opened 9 years ago Closed 9 years ago

[meta] Many tests crash after ending in the new performance tool

Categories

(DevTools :: Performance Tools (Profiler/Timeline), defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: vporof, Unassigned)

References

Details

(Keywords: meta)

Attachments

(1 file)

      No description provided.
Take a look at this gum run: https://treeherder.mozilla.org/#/jobs?repo=gum&revision=2af669f79b9e

Almost all failures are crashes, even though all the checks pass during the test.
No longer depends on: 1129960
Depends on: 1129960
Alias: perf-tool-crashes
Depends on: 1133791
Depends on: 1133793
Depends on: 1133796
Depends on: 1133800
Depends on: 1132370
No longer depends on: 1132370
No longer blocks: perf-tool-v2
Blocks: perf-tool-tests
No longer blocks: enable-perf-tool
Looks like browser_perf-compatibility-04.js is the worst offender, so that could be a good starting point to reproduce/debug this.
For the new performance developer tools, we're seeing a lot from what we believe is the profiler. Tromey has done some debugging in bug 1133791 (comment #1), and seems to be some sort of JIT error. Do any of you have any idea what could be causing this, possible solutions, next steps? Once these crashes are solved, we'll flip the switch to enable in Nightly for the new profiler/timeline tool.

Thanks!
Flags: needinfo?(shu)
Flags: needinfo?(luke)
Flags: needinfo?(jdemooij)
Forwarding to Kannan as this is probably fallout from the new profiler backend.
Flags: needinfo?(jdemooij) → needinfo?(kvijayan)
Flags: needinfo?(luke)
Attached patch debugging.patchSplinter Review
Attaching the patch I used with djvj to debug this. We ended up concluding that a normally dispatched event on the main thread isn't being executed (via `executeSoon`), because of the beachball, which can mean one of three things: 1. the event is removed from the dispatcher, 2. the dispatcher is blocked waiting for something, 3. the dispatcher itself died. Since the debugger server is making heavy use of those, it's entirely possible that while the clients are shutting down, some packets end up being stuck.

We'll be looking more into this on Monday.

I hope there's some delirium tremens in our keg.
Clearing needinfo. Found iloop in _findOptimalTickInterval in devtools/shared/timeline/markers-overview.js
Flags: needinfo?(shu)
Flags: needinfo?(kvijayan)
Thanks shu. Will look at this tomorrow.
Depends on: 1139386
Depends on: 1139388
Infinite loop was fixed in bug 1137503.
Depends on: 1140076
Depends on: 1140074
Depends on: 1140077
Paul, these are the current outstanding crashes on gum: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1133781&hide_resolved=1
Flags: needinfo?(paul)
No longer depends on: 1140074
No longer depends on: 1139388
Talked to shu and I'm not panicking anymore. Removing needinfo
Flags: needinfo?(paul)
Depends on: 1140487
Depends on: 1140848
Depends on: 1142564
Depends on: 1143249
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: