1545835 - Browser stops responding when rendering a file with Blender

Status: RESOLVED INVALID

(Core :: Storage: localStorage & sessionStorage, defect, P3)

Description

[Trevor Rowbotham [:rowbot]]

Not sure if this is the right place for this bug. I'm just going off the call-stack of the ensuing crash-reports. While rendering a file in Blender, Firefox becomes unresponsive on Windows 10 with the latest 64-bit Nightly. A clean profile was used.

Performance profile: https://perfht.ml/2ZnjIJP

STR:

1. Download the Blender Benchmark from https://opendata.blender.org/
2. Extract the app and run the blender-benchmark.exe file.
3. Choose CPU from the drop down (should be the default).
4. Click RUN COMPLETE BENCHMARK.
5. Browse around with Firefox.

AR:
Browser becomes slow (as expected), but after a few minutes will become completely unresponsive until the rendering is halted.

Sample Crash Reports:
bp-1d0fd49a-3fc1-45d4-a5db-7ba020190419
bp-c4d0cf67-8d0c-4a67-930d-2f8c00190419
bp-11124372-d633-4b48-ae3e-ec1f50190419

Comment 1

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

The priority flag is not set for this bug.
:glandium, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Rares Doghi, Desktop QA]

Hi I managed to reproduce this issue On our latest Nightly as well but I couldn't reproduce it on Beta or Release, however even on Nightly I could not get it to crash as much as it just becomes unresponsive and I have to end the process for it.

I'm not sure if Web Storage is the correct component but it might be a good place to start.

Comment 3

[hoang huynh]

Get your daily dose of blending and smoothies - Making news and reviews. With your fruits, meat and vegetables, of course. https://goodfoodblogph.com/

Comment 4

[Andrew Sutherland [:asuth] (he/him)]

Unfortunately the crash reports are no longer available so this bug is no longer actionable, but I do apologize that we were unable to look at the stacks before they expired. The good news is that we have made extensive enhancements to LocalStorage and SessionStorage in the last 2.5+ years, in particular with the Local Storage Next Gen (LSNG) being enabled on release in Bug 1599979 so it's likely that if LocalStorage was involved, the problem was mitigated. That said, it's more likely the problem was due to processes or threads being marked as lower priorities such that blender prevented various Firefox threads from running at all, and I do believe we have addressed some bugs like that in the intervening years as well.