1840384 - Firefox 114.0.2 (64-bit) is broken (supposedly Javascript engine)

Status: UNCONFIRMED

(Core :: Graphics: Canvas2D, defect, P2)

Description

[ayuanx]

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:109.0) Gecko/20100101 Firefox/114.0

Steps to reproduce:

Firefox 114.0.2 (64-bit)
Try https://www.photopea.com/
Select either "new project" or "open from computer".

Actual results:

Picture does not show up, empty black canvas only.
All drawing tools do not work either.
Console shows lots of Javascript error.

One error is very interesting.

Uncaught ReferenceError: gtag is not defined
<anonymous> https://www.photopea.com/:75
www.photopea.com:75:5

But clearly "gtag()" is defined just on line 74. Just one line directly above the error.

	<!-- Global site tag (gtag.js) - Google Analytics -->
	
	<script async src="https://www.googletagmanager.com/gtag/js?id=G-49YR1RB5KP"></script>
	<script>
	  window.dataLayer = window.dataLayer || [];
	  function gtag(){dataLayer.push(arguments);}

------>> gtag("js", new Date()); gtag('config', 'G-49YR1RB5KP'); //gtag("config", "UA-4249565-37");
</script>

Expected results:

Reverting back to Firefox 102.12.0 (64-bit)
Try https://www.photopea.com/ again, everything works.

Comment 1

[ayuanx]

Wait, after I turned off "Use hardware acceleration when available" in Firefox 114.0.2, https://www.photopea.com/ just works!

Comment 2

[ayuanx]

What is more amazing is that once hardware acceleration is turned off, I restarted Firefox 114.0.2, and then re-enabled "Use hardware acceleration when available" as well as "Use recommended performance settings", restarted Firefox 114.0.2 once more, and https://www.photopea.com/ is also working!

Is it a configuration issue caused by Firefox auto update? Because before the auto update to Firefox 114.0.2, https://www.photopea.com/ was working well in Firefox. And I didn't change any settings during or after the auto update.

Comment 3

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

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