This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 242027 - NetBeans ALWAYS hangs after Git / remote / push
Summary: NetBeans ALWAYS hangs after Git / remote / push
Status: RESOLVED DUPLICATE of bug 236101
Alias: None
Product: platform
Classification: Unclassified
Component: JDK Problems (show other bugs)
Version: 8.0
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Assignee: Antonin Nebuzelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 22:16 UTC by rweaver
Modified: 2014-02-19 11:49 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (75.64 KB, text/plain)
2014-02-17 22:16 UTC, rweaver
Details
Thread dump / console output (216.91 KB, text/plain)
2014-02-18 14:11 UTC, rweaver
Details
Updated console output (after kill -9) (222.47 KB, text/plain)
2014-02-19 00:05 UTC, rweaver
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rweaver 2014-02-17 22:16:27 UTC
When I do a push to master/origin (which is on Unfuddle via SSL), NetBeans always hangs. 

It is completely unresponsive, and I've even left it running overnight to see if it ever errors out or comes back.

I end up having to force quit the application.

This was happening since 7.4 at least.

Product Version = NetBeans IDE 8.0 Beta (Build 201401141042)
Operating System = Mac OS X version 10.9.1 running on x86_64
Java; VM; Vendor = 1.7.0_45
Runtime = Java HotSpot(TM) 64-Bit Server VM 24.45-b08
Comment 1 rweaver 2014-02-17 22:16:30 UTC
Created attachment 145332 [details]
IDE log
Comment 2 rweaver 2014-02-18 01:26:54 UTC
Please let me know what I can do to debug this, I'd love to have this fix.

Makes me nervous to have to kill NB every time I push.
Comment 3 Ondrej Vrabec 2014-02-18 08:26:27 UTC
(In reply to rweaver from comment #2)
> Please let me know what I can do to debug this, I'd love to have this fix.
Attach a thread dump when it freezes: http://wiki.netbeans.org/GenerateThreadDump
Comment 4 rweaver 2014-02-18 14:10:50 UTC
Another possible clue - I tried the run from console and did a push with no lockup (had some pending commits and stopped the IDE prior to the push).

Had to do a commit prior to the push to get the lockup.

Attaching the console output.
Comment 5 rweaver 2014-02-18 14:11:49 UTC
Created attachment 145361 [details]
Thread dump / console output
Comment 6 Ondrej Vrabec 2014-02-18 15:39:50 UTC
seems to be a problem with MacOS java, AWT is waiting for an event but does not seem to get any, probably stuck in:
"AppKit Thread" daemon prio=5 tid=0x00007fc358826800 nid=0x507 runnable [0x00007fff595e5000]
   java.lang.Thread.State: RUNNABLE
	at sun.lwawt.macosx.LWCToolkit.doAWTRunLoop(Native Method)
	at sun.lwawt.macosx.LWCToolkit.invokeAndWait(LWCToolkit.java:549)
	at sun.lwawt.macosx.LWCToolkit.invokeAndWait(LWCToolkit.java:489)
	at sun.lwawt.macosx.CAccessibility.invokeAndWait(CAccessibility.java:75)
	at sun.lwawt.macosx.CAccessibility.getFocusOwner(CAccessibility.java:521)

Please Tondo, i think it's a duplicate of another already filed issue, i just do not remember which it was.
Comment 7 Ondrej Vrabec 2014-02-18 15:42:28 UTC
found it: #236101. Caused by a JDK issue, said to be fixed in JDK8 builds

*** This bug has been marked as a duplicate of bug 236101 ***
Comment 8 rweaver 2014-02-19 00:05:39 UTC
Created attachment 145379 [details]
Updated console output (after kill -9)

I came home to find NB still running, so ran a kill -9 (in favor of the kill -QUIT suggested on the help page). A few more lines on the kill, not sure if they are helpful or not.
Comment 9 rweaver 2014-02-19 00:12:17 UTC
Workaround for me is to close down NB after a commit, then restart NB before doing a Git push.

Also have noticed some similar sorts of hangs in the Maven properties panels that seem to be reproducible.
Comment 10 Antonin Nebuzelsky 2014-02-19 11:49:25 UTC
(In reply to rweaver from comment #9)
> Workaround for me

The only real workaround now on OS-X is to use the promoted early access builds of JDK8 (https://jdk8.java.net/download.html) where the JDK bug has been already fixed. Later the next JDK 7 update 55 will also include the fix.