Crash (probably) related to opening a new SSH session
Reported by
patr...@georgi.software,
Apr 16 2017
|
|||
Issue description
IMPORTANT: Your crash has already been automatically reported to our crash system. Please file this bug only if you can provide more information about it.
Chrome Version: 57.0.2987.146
Operating System: Linux 3.14.0
URL (if applicable) where crash occurred: Immediately around this crash, I tried to open a new SSH-in-a-tab window (pnhechapfaindjhompbnflcldabbghjo), got "Es ist ein unerwarteter Fehler aufgetreten, bitte überprüfen Sie die JavaScript-Konsole auf nähere Informationen." (unexpected error, please check javascript console for more information)
Can you reproduce this crash? It's reproducible for me, yes (just open a new SSH session). Existing SSH windows continue to work
Javascript log of that tab, in case it helps figure out what's going on:
Error initializing filesystem: InvalidStateError: An operation that depends on state cached in an interface object was made but the state had changed since it was read from disk. Object {0: "chrome-extension://pnhechapfaindjhompbnflcldabbghjo/js/nassh_deps.concat.js:17287:54"}0: "chrome-extension://pnhechapfaindjhompbnflcldabbghjo/js/nassh_deps.concat.js:17287:54"__proto__: Object
(anonymous) @ nassh_deps.concat.js:17287
nassh_command_instance.js:110 FileSystem init failed:
(anonymous) @ nassh_command_instance.js:110
(anonymous) @ nassh_deps.concat.js:17289
nassh_deps.concat.js:4416 Uncaught TypeError: str.charCodeAt is not a function
at Object.lib.encodeUTF8 (nassh_deps.concat.js:4416)
at hterm.Terminal.IO.println.hterm.Terminal.IO.writelnUTF16 (nassh_deps.concat.js:13729)
at nassh_command_instance.js:113
at nassh_deps.concat.js:17289
lib.encodeUTF8 @ nassh_deps.concat.js:4416
hterm.Terminal.IO.println.hterm.Terminal.IO.writelnUTF16 @ nassh_deps.concat.js:13729
(anonymous) @ nassh_command_instance.js:113
(anonymous) @ nassh_deps.concat.js:17289
****DO NOT CHANGE BELOW THIS LINE****
Crash ID: crash/3409a4fa90000000
,
Apr 19 2017
,
Apr 19 2017
Crash claims to be in "kernel-warning" process type.
,
Apr 20 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Apr 17 2017