OctoPrint / OctoPrint

OctoPrint is the snappy web interface for your 3D printer!
https://octoprint.org
GNU Affero General Public License v3.0
8.22k stars 1.67k forks source link

GCode Viewer hangs with Firefox 128.0 64bit #5044

Closed getgray closed 1 month ago

getgray commented 1 month ago

octoprint-systeminfo-20240714165315.zip

The problem

repeat of #4879

The problem:

Large gcode files (> ~23 MB test file) loaded into OctoPrint will "parse" to a given number (depending on the gcode; it seems to be consistent per file, but varies between files), 81% in this test case, and then stop. Smaller gcode files untested.

Test file worked in Chrome. No content blocking installed.

This was failing with a previous version of FF, but wsa fixed as reported in issue #4879. Has been workign until I send this large file today, it's back to failing with FF.

Did the issue persist even in safe mode?

Yes, it did persist

If you could not test in safe mode, please state why ("currently printing" is NOT an excuse!)

No response

Version of OctoPrint

1.10.2

Operating system running OctoPrint

Octopi

Printer model & used firmware incl. version

No response

Browser and version of browser, operating system running browser

No response

Checklist of files to include below

Additional information & file uploads

No response

github-actions[bot] commented 1 month ago

Hi @getgray!

It looks like you didn't upload a system info bundle as requested by the template. A bundle is required to further process your issue. It contains important logs and system information to be able to put your issue into context and give pointers as to what has happened.

Please edit your original post above and upload a bundle zip file. Actually upload the file please and do not paste some link to a cloud provider, we want to have everything in one place here. Also do not unpack, repack or otherwise modify the bundle or its name, share it exactly like you get it from OctoPrint.

Without the availability of a bundle, your issue will have to be closed.

Thank you for your collaboration.

Thank you @getgray for adding a bundle! Now this can actually get looked at.

getgray commented 1 month ago

By starting the gcode viewer immediately when the print starts, the viewer loads, albeit very slowly. That workaround is good enough, closing bug request.

foosel commented 1 month ago

In any case, this sounds like it is rather a browser bug, so not something I can really fix. If fetching a resource doesn't work, it doesn't work, there's nothing I can do to make it work. I wonder what broke though... It took long enough to see the original issue get fixed on the released browser versions...