Closed
Bug 1130669
Opened 10 years ago
Closed 10 years ago
CRASH: browser_pref-range-changed-render.js | application crashed
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jsantell, Unassigned)
References
Details
In new performance tool, consistently seeing this crash. Any ideas?
TEST-INFO | Main app process: killed by SIGHUP
46 ERROR TEST-UNEXPECTED-FAIL | browser/devtools/performance/test/browser_perf-range-changed-render.js | application terminated with exit code 1
runtests.py | Application ran for: 0:00:32.980060
zombiecheck | Reading PID log: /var/folders/hs/h71qjfd94x34yxmy8qcm9y740000gn/T/tmpI64y_tpidlog
PROCESS-CRASH | browser/devtools/performance/test/browser_perf-range-changed-render.js | application crashed [None]
Reporter | ||
Comment 1•10 years ago
|
||
Commenting out of browser.ini for now
Reporter | ||
Comment 2•10 years ago
|
||
FWIW, I suspect something in this changeset introduced this https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=dee2c8135242
Blocks: enable-perf-tool, perf-tool-v2
Comment 4•10 years ago
|
||
I couldn't reproduce using git master on x86-64 Linux.
I do see some profiler leak reports but they are under the leakcheck threshold.
I'd need more information to continue; like maybe a stack trace of the
crashing thread (or all threads).
Flags: needinfo?(ttromey)
Updated•10 years ago
|
Blocks: perf-tool-crashes
Updated•10 years ago
|
Summary: CRASH: browser_pref-range-changed-render.js → CRASH: browser_pref-range-changed-render.js | application crashed
Updated•10 years ago
|
No longer blocks: perf-tool-v2, enable-perf-tool
Comment 5•10 years ago
|
||
Very likely fixed by bug 1137503
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•