1320559 - Crash in JSObject::is<T>

Status: RESOLVED INCOMPLETE

(Core :: JavaScript Engine, defect)

Description

[Calixte Denizet (:calixte)]

This bug was filed from the Socorro interface and is 
report bp-aaebc7c4-4464-4be3-9ac8-2dc052161127.
=============================================================

There are 4 crashes in nightly with build-id 20161126030207 and in analyzing backtrace they could be a regression introduced by patch https://hg.mozilla.org/mozilla-central/rev?node=d29ab4cddb8299285f431ff521c64712f25ad33e to fix bug 1277368.

Comment 1

[Jan de Mooij [:jandem]]

(In reply to Calixte Denizet (:calixte) from comment #0)
> There are 4 crashes in nightly with build-id 20161126030207 and in analyzing
> backtrace they could be a regression introduced by patch
> https://hg.mozilla.org/mozilla-central/
> rev?node=d29ab4cddb8299285f431ff521c64712f25ad33e to fix bug 1277368.

That's extremely unlikely. The changes there are very simple and this code is very hot so we would see way more crash reports if we broke something there.

I don't see any crashes on Nightly for the last 7 days. Also notice that the crash report in comment 0 has an uptime of 0 seconds and a "last crash" time of 1 second. Sure, there could still be a real bug causing that, but it usually means some kind of hardware thing or external software messing with stuff. I wouldn't be surprised if the 4 reports were all from the same user.

Let's reopen or file a new bug if there's actually a crash spike here.