This App cannot be launched while no chrome window is running.

55 views
Skip to first unread message

sunx...@gmail.com

unread,
Mar 14, 2016, 1:10:07 PM3/14/16
to chromium-hterm
Hello,

I'm under Windows 10 and I'm using chrome app launcher to launch this app. in 'Open as window' mode.
I noticed that when I launch this app while no chrome window is running, the app will show blank and I can do nothing. I have to launch it again and since the last blank window is a chrome window running, the app can be launched this time.

Is this a bug or it just happens to me?

Please help me fix it.

Thanks.

Mike Frysinger

unread,
Mar 14, 2016, 1:21:00 PM3/14/16
to sunx...@gmail.com, chromium-hterm
open up the console (ctrl+shift+j) and see if there are any interesting errors there
-mike

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/e94bad26-826c-403c-b0b6-8616541c62d3%40chromium.org.

Sun Xuzhan

unread,
Mar 14, 2016, 1:42:41 PM3/14/16
to Mike Frysinger, chromium-hterm
Yes, It look like this:

extensions::uncaught_exception_handler:8 Error in response to runtime.getBackgroundPage: TypeError: Cannot read property 'onUpdateAvailable' of undefined
    at chrome-extension://pnhechapfaindjhompbnflcldabbghjo/js/nassh_main.js:62:10
    at window.onload (chrome-extension://pnhechapfaindjhompbnflcldabbghjo/js/nassh_main.js:52:18)handler @ extensions::uncaught_exception_handler:8

sunx...@gmail.com

unread,
Mar 14, 2016, 1:43:09 PM3/14/16
to chromium-hterm, sunx...@gmail.com
Like this:

extensions::uncaught_exception_handler:8 Error in response to runtime.getBackgroundPage: TypeError: Cannot read property 'onUpdateAvailable' of undefined
    at chrome-extension://pnhechapfaindjhompbnflcldabbghjo/js/nassh_main.js:62:10
    at window.onload (chrome-extension://pnhechapfaindjhompbnflcldabbghjo/js/nassh_main.js:52:18)handler @ extensions::uncaught_exception_handler:8

Mike Frysinger

unread,
Mar 15, 2016, 5:46:59 PM3/15/16
to Sun Xuzhan, chromium-hterm
i think that's just a long standing bug.  if the background page didn't launch/initialize fast enough, the foreground window crashes trying to access the uninitialized app state.  you should be able to just close the main window and re-launch the app and it should work.

not sure what the best answer is here.  seems like the code uses the bg app just for onUpdateAvailable notifications.  if we skipped those entirely if we launched too fast, it doesn't seem like the end of the world.
-mike

Sun Xuzhan

unread,
Mar 28, 2016, 11:09:14 AM3/28/16
to Mike Frysinger, chromium-hterm
So it seems that I do not have a walk-around method but to try launching again?
Thanks for your explaination:D

Mike Frysinger

unread,
Apr 6, 2016, 11:28:31 PM4/6/16
to Sun Xuzhan, chromium-hterm

Sun Xuzhan

unread,
Apr 6, 2016, 11:30:55 PM4/6/16
to Mike Frysinger, chromium-hterm
Thank you for your effort:D
Reply all
Reply to author
Forward
0 new messages