]
Jiri Peterka commented on JBDS-3057:
------------------------------------
Yes, it's Gnome Shell "issue", either Gnome Shell is more strict in terms of
application responsiveness or possibly applications are slower on Gnome Shell. Maybe
both.
JBDS causes "not responding" message on RHEL
--------------------------------------------
Key: JBDS-3057
URL:
https://issues.jboss.org/browse/JBDS-3057
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.1.1.GA
Environment: RHEL 7 Beta
OpenJDK 1.7
JBDS 7.1.1
Reporter: Martin Malina
Attachments: jbds-not-responding.png
I was smoke testing JBDS 7 on RHEL 7 Beta and every time I started JBDS with a new
workspace, I got a "not responding" window where I could either force quit JBDS
or wait.
Obviously this is due to some limit that is set in the OS and when reached, this popup is
shown.
On subsequent starts of JBDS with the same workspace, this does not happen.
The system was a VirtualBox VM run on Windows, but there was nothing else happening on
the machine, so this shouldn't slow things down too much. Also, the machine has 8 GB
of RAM out of which 4 GB was dedicated to the VM. So I don't think the HW is
particularly slow.
I understand that this JIRA is very vague, but maybe it's worth trying to find if
it's caused by some synchronous processes that we run at JBDS start.