nw.js: NWJS sometimes doesn't re-open until "name" is changed

It appears the "name" field in the package manifest cannot contain the : character. NW.js just crashes with no output (even with logging enabled), causing a considerable amount of headache.

nw.js v0.50.1
Node v15.3.0
Chromium 87.0.4280.66
commit hash: 2d5b629-518f361-e10550e-d168d6d

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 22 (2 by maintainers)

Most upvoted comments

Ok i share this because its made me think about this problem !!! 😁 It is likely that can came from chromium accessibility features. Chromium can be unstable with some external software accessibility ! --disable-renderer-accessibility in vscode and in nwjs can fix this weird ghost issue !

https://github.com/microsoft/vscode/issues/107016#issuecomment-697713704 https://github.com/microsoft/vscode/issues/113553

Thas mean check all background software in your machine, they can break vscode,nwjs,electrons… because(chromium). like: *Mouses macro softwares *Keyboards macro softwares … ext

here video proofff !! https://youtu.be/14AKtLqlbtE

Its just a hint, i dont know if it can related , but seem make sence since we know chromium is unstable with some external software’s and process !

Also in my last screen upper, you can see by mistake i have this hell microsoftKeyboard open who you can see in the video!!! Can explain this weird behavior and memory leak.

jonlepage on Jan 6, 2021

+++++++++++++1 sometimes not open! but created process! v0.50.2

vulcan9 on Dec 21, 2020