1313822 - Crash in nsTimerImpl::Fire

Status: REOPENED

(Core :: DOM: Workers, defect, P3)

Description

[Benoit Girard (:BenWa)]

This bug was filed from the Socorro interface and is 
report bp-39e7822e-279b-48f1-9561-0b4432161029.
=============================================================

Just had two crashes with this stack today on Nightly.

Comment 1

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Due to the low volume, tracking as P3 for now.

Comment 2

[Ben Kelly [:bkelly, not reviewing]]

I don't know if its related, but I found the interrupt-gc-on-tab-switch code was crashing worker threads today.  Might be related.  The diagnostic assert did not show in the stack traces until I did a debug build.

Comment 3

[Markus Stange [:mstange]]

I hit this bug today (twice) while the profiler was active. Because of that and because of the fact that BenWa filed this bug, I think it may have to do with the profiler.

Comment 4

[Benoit Girard (:BenWa)]

Very possible. I've got the profiler toggled off ATM. I'll let you know if I get this crash with the profiler disabled.

Comment 5

[Astley Chen (inactive)]

We have bug 1323804 which root cause(racing during timer firing) is possibly similar to this bug.

Comment 6

[Julien Cristau [:jcristau] (back April 22)]

Mass wontfix for bugs affecting firefox 52.

Comment 7

[Jens Stutte [:jstutte]]

I have no historical data in order to see, if bug 1323804 's fix did improve the situation, but it is definitely not yet solved entirely. :BenWa, can we see in the crashstats, if the profiler was active during the crash?

Comment 8

[Benoit Girard (:BenWa)]

Not that I'm aware.

Comment 9

[Pablo]

Reopening bug since there are crash reports in the last 6 months.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Since the crash volume is low (less than 15 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.