openjdk team mailing list archive

[Alan Ferguson <Alan.Ferguson@xxxxxxxxxxxx>]

Joachim Durchholz (jo-durchholz) offered a fix to the locking problem
(entry #27). I had the same problem. It took several tries to get
netBeans 8.1 started (using java-7-openjdk), and then it would lock
occasionally when it was started (at the ...Starting Modules). It was
finally working reasonably well when I tried to get the red, vertical
line removed. After that, it locked up before the column for the red
line could be changed, and did not load after that at all, after 4 or 5
tries.

I commented out the line in the accessibility.properties file, and
NetBeans 8.1 has loaded every time since that fix (only 3 or 4 times so
far). A benefit was that I was also able to change te excessive column
to line 200, and the text box in which the column number was contained
was now wide enough to see all 3 digits (200).

I am just starting to try NetBeans now, so I don't consider myself an
expert on this development system.

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-8 in Ubuntu.
https://bugs.launchpad.net/bugs/1510009

Title:
  Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK
  interaction

Status in JOSM:
  Unknown
Status in openjdk-8 package in Ubuntu:
  Incomplete
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  Since upgrading to Ubuntu 15.10 from Ubuntu 15.04, the various GUI
  applications that I run, including Netbeans and Minecraft have been
  suffering from dead/waitlocks which prevent them from operating
  properly. Since I have reproduced this issue these two completely
  different codebases, I am moving the bug further upstream.

  The original Netbeans bug report can be viewed here: https://netbeans.org/bugzilla/show_bug.cgi?id=256124
  Essentially, during routine interaction and calling of various AWT methods, somewhere between 8u45 (15.04) and 8u66 (15.10), something broke causing the application to hang intermittently when these methods are called.

  Some sample jstack traces are attached, the issue should be fairly
  obvious to spot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/josm/+bug/1510009/+subscriptions