This bug was filed from the Socorro interface and is report bp-ea445ca1-3f30-45b3-9ddd-be58b0170527. ============================================================= I can consistently reproduce this crash on two different computers. Go to https://www.reittiopas.fi/ and just use the site for a while and you'll get this crash sooner or later. I also got the following crash signature once: js::jit::BailoutIonToBaseline https://crash-stats.mozilla.com/report/index/b974e836-cbf5-4268-ab10-75c130170527
Has STR: --- → yes
It doesn't crash for me on Win 7.
77% of the crashes on recent versions of Firefox are happening on MOZ_CRASH(No native code for this pc) at https://hg.mozilla.org/releases/mozilla-release/annotate/afa87f9be3a8/js/src/jit/BaselineJIT.cpp#l895 Kannan, any idea if this assertion is actionable?  https://crash-stats.mozilla.com/signature/?version=60.0a1&version=59.0b&version=59.0b9&version=59.0b10&version=59.0b7&version=59.0b8&version=59.0b6&version=59.0b5&version=59.0b4&version=59.0b3&version=59.0a1&version=58.0.2&version=58.0.1&version=58.0b&version=58.0&version=58.0b99&version=58.0b16&version=58.0b15&version=58.0b14&version=58.0b13&version=58.0b12&version=58.0b11&version=58.0b10&version=58.0b9&version=58.0b8&version=58.0b7&version=58.0b6&version=58.0b5&version=58.0b4&version=58.0b3&version=57.0.4&version=57.0.3&version=57.0.2&version=57.0.1&version=57.0&signature=js%3A%3Ajit%3A%3ABaselineScript%3A%3AnativeCodeForPC&date=%3E%3D2017-08-15T17%3A22%3A18.000Z&date=%3C2018-02-15T17%3A22%3A18.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_columns=moz_crash_reason&_sort=version&_sort=uptime&_sort=-date&page=1
Severity: critical → normal
Status: UNCONFIRMED → NEW
Has STR: yes → ---
status-firefox60: --- → fix-optional
Ever confirmed: true
Priority: -- → P3
This should be actionable. How urgent is this, and how high of a crasher is this? It seems pretty low-frequency. If we can get a repro for this it should be very actionable.
(In reply to Kannan Vijayan [:djvj] from comment #3) > This should be actionable. Can you detail what would be the conditions needed to reach this assertion, and how fixing this issue should be approached?
Could be related to running the gecko-profiler? https://crash-stats.mozilla.com/report/index/d0349b47-46f6-4a07-b6ef-c65470180627
(In reply to Paul Bone [:pbone] from comment #5) > Could be related to running the gecko-profiler? Maybe! I just ran into this crash, just after capturing a profile with perf-html.io. My crash report is bp-d16a027c-d908-49e8-a55f-1b5b10180913 . The crash happened just after the profile was displayed -- possibly while resolving symbols.
The crash is almost definitely related to jit-coach, and native stack walking. These crashes are basically impossible to reproduce and happen randomly. The proper resolution is to implement bug 1426134 and get rid of the ad-hoc, extremely fragile stack-walking that explicitly keeps itself aware of the stack structure of every type of frame. This is just extremely prone to bitrot, and crashes are very hard to diagnose.
You need to log in before you can comment on or make changes to this bug.