You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using accessibility mode can sometime end up with trace as:
TypeError: Cannot set property 'textContent' of undefined
at AccessibilityManager../node_modules/xterm/lib/AccessibilityManager.js.AccessibilityManager._renderRows (...)
at RenderDebouncer../node_modules/xterm/lib/ui/RenderDebouncer.js.RenderDebouncer._innerRefresh (...)
This is new regression seen only in version 3.13.0, version 3.12.2 was not affected.
In general this is hard to reproduce, it happens in our CI, or I can only reproduce it with very high load on my machine and running tests in loop.
I know this is no reproducer, possibly just conditionally check that these elements are present? Seems related to 4c3082c924ac or more general to #2026
The text was updated successfully, but these errors were encountered:
marusak
added a commit
to marusak/cockpit
that referenced
this issue
May 14, 2019
This reverts commit 55f71b8.
The reverted commit was introduced in #11797 but later on was noticed
that sometimes xterm can crash. Reported to xtermjs/xterm.js#2082Closes#11822
Using accessibility mode can sometime end up with trace as:
This is new regression seen only in version
3.13.0
, version3.12.2
was not affected.In general this is hard to reproduce, it happens in our CI, or I can only reproduce it with very high load on my machine and running tests in loop.
Possible place of happening https://github.com/xtermjs/xterm.js/blob/master/src/AccessibilityManager.ts#L252
I know this is no reproducer, possibly just conditionally check that these elements are present? Seems related to 4c3082c924ac or more general to #2026
The text was updated successfully, but these errors were encountered: