840502 - Crash with EXC_BAD_ACCESS in mozilla:gfx:DrawTargetCG::DrawSurface

Status: RESOLVED WORKSFORME

(Core :: Graphics: Canvas2D, defect)

Description

[Ivo Wetzel]

Attachment: crash.html

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17

Steps to reproduce:

This happens in a HTML5 Canvas game, it instantly crashes FX 18.0.1 through 21 on Mac OSX 10.7.4 and 10.8.2 (don't have any other OSX Version available right now).

Does not happen on Windows as far as I can tell.

A reduced test case is attached which will kill FX as soon as the page is loaded in the affected Firefox / OSX versions:



Actual results:

Seems like it tries to draw the rect at the lower edge of the target canvas (with some minimal rotation applied to it?) and that somehow fails.


Expected results:

Nothing, as the draw call is outside the target canvas. Chrome and the Windows Version of Firefox show the target canvas completely empty.

Comment 1

[Scoobidiver (away)]

Please provide the matching crash ID from the about:crashes page.

Comment 2

[Ivo Wetzel]

(In reply to Scoobidiver from comment #1)
> Please provide the matching crash ID from the about:crashes page.

Crash Report: https://crash-stats.mozilla.com/report/pending/24ca0f24-15ad-418c-8035-ee96e2130212

Comment 3

[Scoobidiver (away)]

(In reply to Ivo Wetzel from comment #2)
> https://crash-stats.mozilla.com/report/pending/24ca0f24-15ad-418c-8035-
> ee96e2130212
There are no Firefox components in the stack trace, only those of Mac OS X.

Where does mozilla:gfx:DrawTargetCG::DrawSurface come from?

Does it happen in Safe Mode (see https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode)?

Comment 4

[Ivo Wetzel]

I ran a trunk build through XCode for debugging purposes and it seems strange that it's not included in the crash report created by Firefox.


Unfortunately, I don't know how to get the stack trace out of XCode, but I can attach a screenshot (yes, not perfect, I know).

Comment 5

[Ivo Wetzel]

Attachment: XCode StackTrace of the Crash

Comment 6

[Scoobidiver (away)]

What about the safe mode?

Comment 7

[Ivo Wetzel]

Crashes in safe mode too.

Crash Report here: https://crash-stats.mozilla.com/report/index/3a0e5a62-fe67-4ed4-956d-09d3c2130212

Comment 8

[u279076]

Ivo, is this still reproducible for you?

Comment 9

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.

Comment 10

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Reopening because crash bugs **with testcases** should not be resolved **as WONTFIX** based on queries of crash-stats.  Other resolutions may be appropriate for other reasons.

(Crash signatures are not the same as bug identity; they're merely a search aid to find and group similar crashes.  The bug may still be present, but the signature may have changed slightly, or the bug may even still be present with the same signature but there are simply no recent reports of crashes in that function.)

Comment 11

[Marcela (Please NI request to Brindusa Tot)]

Closing this as Resolved-Worksforme since there were no crashes in the last 6 months for this signature.