Closed Bug 1240654 Opened 8 years ago Closed 8 years ago

Firefox crashing when rendering canvas

Categories

(Core :: Graphics: Canvas2D, defect)

43 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: me, Unassigned)

Details

(Keywords: crashreportid, Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030

Steps to reproduce:

1. Open https://cryptowat.ch
2. Drag the candlestick chart back-and-forth horizontally
3. After doing this for 20-60 seconds, Firefox will crash




Actual results:

Firefox crashes with "EXC_BAD_ACCESS / KERN_INVALID_ADDRESS".

I *think* this is an issue with canvas, since canvas rendering is most of the work being done when the chart is dragged around like that. However I am not experienced enough debugging crashes like this to pinpoint where in the JavaScript code the crash actually originates.


Expected results:

Firefox should not have crashed, and in fact it seems this only started to happen in Firefox 43.
I am unable to reproduce this in Firefox 42, but it consistently crashes in 43. I have gotten reports of the same from several users of the Cryptowatch website.
I've been unable to reproduce this with Firefox Nightly 46.0a1 on my 2013 Retina Macbook Pro 13". Please test this with the latest Nightly to see if it reproduces. If it does, please provide the IDs for any crashes you reported from about:crashes and a copy of your about:support page. Thanks.
Keywords: crashreportid
Whiteboard: [gfx-noted]
I just tried and couldn't reproduce on Nightly. Tried again on 43 and it crashed almost immediately. I'll test on Nightly before making bug reports from now on. Thanks a lot for the quick response! I appreciate it.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
(In reply to me from comment #3)
> I just tried and couldn't reproduce on Nightly.

Does turning multi-process off in Nightly enable you to reproduce the crash?
You need to log in before you can comment on or make changes to this bug.