Browser becomes unresponsive #1699

Open
jammi opened this Issue Jan 10, 2017 · 12 comments

Projects

None yet

3 participants

@jammi
jammi commented Jan 10, 2017

What were you doing?

Left the OctoPrint page open.

What did you expect to happen?

The page to stay responsive.

What happened instead?

Becomes unresponsive.

Branch & Commit or Version of OctoPrint

Version: 1.3.0.post0.dev0+g7f5d03d (master branch)

Printer model & used firmware incl. version

Wanhao Duplicator i3 v2.1, Repetier 0.9

Browser and Version of Browser, Operating System running Browser

Safari, 10.0.2 on macOS Sierra, 9.x on iPad iOS 9.

Link to octoprint.log

https://gist.github.com/jammi/8299c0855b88a6aa8e63ffc6314c6824

Link to contents of terminal tab or serial.log

Nothing unusual, just Repetier doing its Recv: wait thing

Link to contents of Javascript console in the browser

Screenshot(s) showing the problem:

Safari console, corresponding 404 for the sourcemaps when opening the console half an hour after the page was loaded and become unresponsive meanwhile, the rest in it is "normal":
http://i.imgur.com/y5Pi28V.png

I have read the FAQ.

@foosel
Owner
foosel commented Jan 10, 2017

Infos from IRC:

  • websocket stays responsive longer then rest
  • buttons backed by a REST request stop working, REST request isn't even attempted
  • nothing logged in JS console or network tab
  • strictly local functions (filtering the terminal, opening/closing accordions and the like) continue to work

Currently unreproduced.

@foosel
Owner
foosel commented Jan 10, 2017

Potentially related to #1523 ?

@jammi
jammi commented Jan 10, 2017

Possibly yes, the only thing apart from the System menu and some local UI elements that became responsive was the Disconnect button in the Connnection accordion, and hitting Connect after that kicked it up. This was after several reloads of no socket activity, at which point I'd normally have restarted OctoPrint to get it going.

@jammi
jammi commented Jan 10, 2017

While the OctoPrint window on the Mac had started showing just 0°C / 0°C after reloads, the page on the iPad still read some ambient room temperature from the printer, but nothing there was any more responsive than on the Mac.

@foosel
Owner
foosel commented Jan 10, 2017

If the disconnect button works, it's not the communication with the backend that's the problem. Based on you saying that you "couldn't send commands" on IRC, I assume now that the problem rather lies with the communication to your printer breaking but the communication between OctoPrint's front-end and backend still working just fine?

I'm utterly confused now what the actual issue is you are experiencing. Please describe exactly, with as much detail as possible, what works, what doesn't, and what exactly makes it work again. I for one am currently completely in the unclear on what you are actually looking at ;)

@foosel
Owner
foosel commented Jan 10, 2017

If you want, a screencast on YouTube showing the problem would also be very helpful here I think.

@jammi
jammi commented Jan 10, 2017

Well, when nothing in the main view responds, seems like ui-only features are active and there's no indication of responsiveness and there are no errors, and you don't want to start a new print on a potentially unstable system, what can you conclude?

@foosel
Owner
foosel commented Jan 10, 2017

what can you conclude

Actually, you shouldn't conclude anything but simply describe exactly what you are seeing, as detailed and descriptive as possible ("Becomes unresponsive." is pretty non-descriptive and can mean a multitude of things), especially if you don't know how stuff fits together :)

That prevents misunderstandings on both sides as we had here - I honestly thought you were looking at network communication issues based on your descriptions here and on IRC. And preventing misunderstandings in turn saves valuable time otherwise lost on useless back-and-forth while trying to understand and ideally solve an issue (be it through a bug fix or a configuration change).

@foosel
Owner
foosel commented Jan 20, 2017

@bolsoncerrado that's what I thought too, but after some more details @jammi actually appears to be running into issues where his printer stops responding to commands sent via serial, with the web frontend itself staying completely responsive.

@jammi
jammi commented Jan 21, 2017 edited

I later got UI hangs as well, where the printer was responsive and traffic was otherwise ongoing, but UI buttons wouldn't pass on, like terminal command line entry not being sent or cleared, control tab things not doing anything and so forth. The incident while opening this issue could've overlapped with such an event. Left-hand side panel worked, the right-hand side panels didn't. Disconnect-Connect didn't resolve, no number of reloads of the browser window on either device would work either. Restarting octoprint in this case was the only way to restore functionality. So basically I got the same thing I've got earlier many times, but probably not related to printer comms like the one 10 days ago.

@bolsoncerrado
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment