Uploaded image for project: 'NetBeans'
  1. NetBeans
  2. NETBEANS-4866

Netbean can become a zombie process with no IDE UI after Banner.

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 11.1, 12.1
    • Fix Version/s: None
    • Component/s: ide - UI
    • Labels:
      None
    • Environment:

      Windows 10 Professional, latest update, and AdoptOpenJDK jdk-15.0.0.36-hotspot

      Description

      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.

       

        Attachments

        1. messages.zip
          10 kB
          Finally Not Oracle

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              finally-not-oracle Finally Not Oracle
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: