NWJS sometimes doesn't re-open until "name" is changed
See original GitHub issueIt 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
Issue Analytics
- State:
- Created 3 years ago
- Comments:22 (2 by maintainers)
Top Results From Across the Web
NW.js Documentation
js should open the main window. Event: added (id, name, order, type, primary). Behavior Changed This feature is changed in 0.13.0 ...
Read more >Steam/Game-specific troubleshooting - ArchWiki
This problem was found after the kernel update to 5.17: the game does not start properly. A possible workaround is to change ~/.local/share/Steam/steamapps/ ......
Read more >Changelog - Cypress Documentation
Before this change, a spec was scaffolded with either the wrong spec name or ... component testing spec in open mode does not...
Read more >How to Update NW.js to Dramatically improve Game ...
But it's possible that you will start getting the NW.js profile error ... could be required for Mac, in order to accommodate that...
Read more >TROUBLESHOOTING :: OMORI General Discussions
"MY GAME DOES NOT START AT LAUNCH, BUT I CAN SEE THE PROCESS IN THE TASK ... NW.js, which sometimes does not work...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub 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.+++++++++++++1 sometimes not open! but created process! v0.50.2