Webcam Stream Loading... Safari

[KaJashey]

The problem

The problem: Octoprint 1.9.2 and earlier. Intermittently when viewing the control tab in Safari I get a message "Webcam Stream Loading..." and the video does not load.

To fix the problem: Clear cache and restart Safari:

To cause the problem to reoccur: Open two browser tabes with the Octoprint: Control tab open. The second browser tab will have the "Webcam Stream Loading..." message while the first plays video. Closing those two browser tabs and opening another gets the "Webcam Stream Loading..." message. This persists till cache is cleared and browser is restarted.

This doesn't not happen on Chrome: Chrome can have two browser tabs with the control window open and video streams to each.

Will try to report to Apple/Safari team as well

Did the issue persist even in safe mode?

I cannot test this issue in safe mode (state why below)

If you could not test in safe mode, please state why

Currently printing a big print

Version of OctoPrint

1.9.2

Operating system running OctoPrint

Linux

Printer model & used firmware incl. version

Prusa Mk3S+ - Firmware 3.13.0

Browser and version of browser, operating system running browser

Safari 16.5.2 /605.1.15 Mac OS Ventura 13.4.1(c)

Checklist of files to include below

• Systeminfo Bundle (always include!)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)
• Screenshots and/or videos showing the problem (always include in case of issues with the user interface)
• GCODE file with which to reproduce (always include in case of issues with GCODE analysis or printing behaviour)

Additional information & file uploads

systeminfo.txt.zip

[github-actions]

Hi @KaJashey!

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.

[foosel]

If you could not test in safe mode, please state why

Currently printing a big print

As it says right in the issue form, "currently printing a big print" is not an excuse to not test in safe mode! Please finish your big print, then test in safe mode, then get back to us on whether the issue persists.

This is not to annoy you, this is because a lot of issues are caused by third party plugins which get disabled in safe mode, and debugging stuff that is not even part of core OctoPrint costs valuable time that is then not available for hunting actual core bugs or improving things in general for everyone.

[KaJashey]

My Apologies. I finished the big print and got a chance to test with Octoprint in safe mode. The issue still occurs in safe mode.

To add to the importance of this issue it also occurs at random not just with the two browser tabs open. The two browser tabs on control is just a guaranteed way to trigger it. So can occurs randomly and doesn't go away. Deleting cache is not something commonly done on Safari. The user has to enable a develop menu and chose from some advanced options.

I have reported it to Apple as it may be more of a Safari problem. I haven't heard anything back

Also the start print overly is never show on the temperature panel. That little notice of when the print was started.

[wolfgangrumpf]

I actually am having a problem that may be related - webcam was working fine then just stopped working; if I run sudo service camera-streamer restart it typically fixes it, at least for a while....

[foosel]

@wolfgangrumpf that rather sounds like ayufan/camera-streamer#94

[foosel]

Closing as there's been no additional information provided in a year by the OP, and it's likely a Safari issue in either case and thus out of scope here.