1778475 - WebGL crash. No crash report

Status: RESOLVED INCOMPLETE

(Core :: Graphics: CanvasWebGL, defect)

Description

[Marco]

Attachment: Immagine 2022-07-07 131916.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

Often I like play to https://gulper.io/
Sometimes in a month and on many try Firefox crash the game showing an error message about WebGL. I need close and re-open Firefox to be able to start a new game. My game was lost because of Firefox crash with a WebGL error that say is not installed. This happen since long time with different versions of Firefox.

Actual results:

After playing sometimes WebGL get in crash in Firefox and a page with the error is showed

Expected results:

Not having any crash with no interruption and no error about WebGL

Comment 1

[Marco]

Attachment: Immagine 2022-07-07 131939.png

Comment 2

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

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: CanvasWebGL' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Marco]

Opened this report yesterday and today I had again a crash of WebGL while using the gulper.io website.
I don't like this WebGL software, is not working well on browsers... and with Firefox I have crashes.

I checked and seems there is no crash report on Firefox because maybe the browser was not crashing, simply WebGL stop to work and the screen on the browser say to check if the component is present.

Comment 4

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

The severity field is not set for this bug.
:aosmond, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 5

[Wayne Mery (:wsmwk)]

See https://firefox-source-docs.mozilla.org/contributing/debugging/stacktrace_windbg.html#how-to-get-a-stacktrace-with-windbg for instructions of getting a stacktrace

Comment 6

[Marco]

Sorry but currently I never use anymore WebGL and website where this issue occurs even if was not an issue of the website but the WebGL and Firefox. I am unable to provide logs or more info about this bug.

Also if is unresolved, feel free to close if you cannot do nothing without additional info from me,
Thanks

Leave it open if you can investigate more.

Comment 7

[Kelsey Gilbert [:jgilbert]]

Ok, thanks for the report! We'll get back to you quicker next time! :)