[jira] [Created] (NETBEANS-4866) Netbean can become a zombie process with no IDE UI after Banner.

["Finally Not Oracle (Jira)" <ji...@apache.org>]

Finally Not Oracle created NETBEANS-4866:
--------------------------------------------

             Summary: Netbean can become a zombie process with no IDE UI after Banner.
                 Key: NETBEANS-4866
                 URL: https://issues.apache.org/jira/browse/NETBEANS-4866
             Project: NetBeans
          Issue Type: Bug
          Components: ide - UI
    Affects Versions: 11.1, 12.1
         Environment: Windows 10 Professional, latest update, and AdoptOpenJDK jdk-15.0.0.36-hotspot
            Reporter: Finally Not Oracle
         Attachments: messages.zip

The latest zombie process incident happened when clicked the restart prompt after disable the C++ plugin.  Multiple starts, temporary Banner display, minute waits, process kills, and required (!) manual lock file deletes later, but still no visible IDE UI!

I've attached 12.1\var\log\messages.log in a zip file.

I suspect that what is happening is that some of the saved state becomes invalid or there is a module conflict, so NetBeans is unable to show a window, so effectively becomes a zombie process.  I managed to resolve prior incidents by deleting the config directory in the profile directory, but that is a horrible solution!

My suggestion is that, at startup, any saved state or plugin which prevents IDE UI display is disabled or reverted to defaults, the repaired state saved, and NetBeans exits, maybe with  counter limited restarts.

BTW:
 * I hope that this isn't caused by the AWT/Swing queue stalling, because some stupid code is doing busy-work on the AWT/Swing thread, which should be done off it.
 * It seems really stupid to attempt any access any project folders before the IDE UI is _confirmed as visible_, say by an Atomic flag or event listener, because I had to close another process locking some project git files, to stop premature/spurious deadlock message noise being logged in message.log...
 * BTW: Isn't about time that the lame lock file, in the profile folder, is replaced by try allocation of a keyed unique OS resource, like a localhost server socket, from a range of configured port addresses, to avoid the pointless drudgery of manually deleted it  after the NetBeans process has died without deleting it, say from a crash or process kill.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists