Open Bug 1924573 Opened 1 year ago Updated 1 year ago

Visiting of the demo located on https://codepen.io/mayankleoboy1/full/wvbeZaG makes Firefox and macOS unresponsive

Categories

(Core :: Graphics: WebRender, defect, P3)

Firefox 133
defect

Tracking

()

UNCONFIRMED

People

(Reporter: mkem, Assigned: bradwerth)

Details

Attachments

(1 file)

Attached file about-support.txt

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:133.0) Gecko/20100101 Firefox/133.0

Steps to reproduce:

I visited demo located on this address https://codepen.io/mayankleoboy1/full/wvbeZaG and once the page is loaded then Firefox and even macOS become unresponsive. Rendering of the demo does not work. I discovered this demo in the Bug 1901190 which was resolved recently but it does not work on macOS.

Actual results:

Firefox and macOS become unresponsive. Rendering does not work.

Expected results:

The demo should work normally as in Safari.

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

Component: Untriaged → Widget: Cocoa
Product: Firefox → Core

I'm unable to reproduce this on Sequoia 15.1 with a local build from current m-c. I understand that you say that Firefox and even macOS become unresponsive. Are you still able to capture a performance profile, or is it not responsive enough to do so? https://profiler.firefox.com/

Hi, if I use standard mode of Firefox then I'm not able to capture anything. Either Firefox crashes or freezes completely. I was able to see that Firefox's main process oscilates between 70 - 100% CPU usage and "kernel_task" process exceeds 100% CPU usage too. Here are some crashes:

https://crash-stats.mozilla.org/report/index/d1e049a7-5806-4dd7-8cdc-026120241015
https://crash-stats.mozilla.org/report/index/84af1814-1b16-4e56-9957-93bdd0241015
https://crash-stats.mozilla.org/report/index/5799348e-a65b-4454-81f9-a92b50241015

Crashes happened mostly in case of standard mode of Firefox and try to open the link in private window.

However if I used Troubleshoot Mode I was able to capture this:

https://share.firefox.dev/4eK5vNw

Main process was around 100% however Firefox was able to at least close the tab with the opened link after some time, so that I was able to capture something. Interestingly "kernel_task" process was busy normally without excessive usage, so that macOS was responsive normally too.

I've filed bug 1924865 about the crash. Let's keep this bug about the hang and system lock-up.

Component: Widget: Cocoa → Graphics: WebRender

Web content freezing Firefox, that sounds kind of bad. Moving to team triage to find an owner.

Blocks: gfx-triage

I will try to reproduce on similar hardware.

Assignee: nobody → bwerth
Severity: -- → S3
Priority: -- → P3
No longer blocks: gfx-triage

Note: Heavy artifacting in both Edge and Chrome.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: