Fehlermeldung: ResizeObserver loop completed with undelivered notifications.
- Thread starter hackcat
- Start date
Hi, sorry to change to English but the search only turned up this post. I click to fullscreen after VM started and the following is showing, even when I un-maximize the screen. It does not appear there is a way to clear it.
In the tasks log, when starting this VM for the first time, it shows:
VM 370 not running
TASK ERROR: Failed to run vncproxy.
Possibly this displayed error is due to the initial error. To be clear, the displayed error occurred only when I maximized the VNC window using the sidebar 2nd button.
EDIT 1: It's in the noVNC_fallback_error div.
EDIT 2: The tasks error is unrelated. I stopped the VM, restarted it and navigated to the console tab AFTER starting...no error in tasks. However, upon maximize the displayed error returns.
EDIT 3: I saw the javascript event for click and now see it goes away with a click.
In the tasks log, when starting this VM for the first time, it shows:
VM 370 not running
TASK ERROR: Failed to run vncproxy.
Possibly this displayed error is due to the initial error. To be clear, the displayed error occurred only when I maximized the VNC window using the sidebar 2nd button.
EDIT 1: It's in the noVNC_fallback_error div.
EDIT 2: The tasks error is unrelated. I stopped the VM, restarted it and navigated to the console tab AFTER starting...no error in tasks. However, upon maximize the displayed error returns.
EDIT 3: I saw the javascript event for click and now see it goes away with a click.
Last edited:
thanks, i can reproduce it (sometimes) in firefox, not in chrome though... can you open a bug here (so we can better track it?): https://bugzilla.proxmox.com
Yes, I run FF Developer, sorry should have noted that.
I have just read in the noVNC repo issues that it's a known bug but it appears it's a Firefox race. Seems to occur when opened in an iframe, and as you described, no issues in Chrome. As it's not a Proxmox bug, should we still add to bug tracker?
NoVNC ref: https://github.com/novnc/noVNC/issues/1604
Firefox ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1685038
I have just read in the noVNC repo issues that it's a known bug but it appears it's a Firefox race. Seems to occur when opened in an iframe, and as you described, no issues in Chrome. As it's not a Proxmox bug, should we still add to bug tracker?
NoVNC ref: https://github.com/novnc/noVNC/issues/1604
Firefox ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1685038
