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 16084 - Mouse stops working in new IDE windows after a while
Summary: Mouse stops working in new IDE windows after a while
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Windows 95/98
: P1 blocker (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-01 17:12 UTC by pepijn
Modified: 2008-12-23 14:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ide.log (3.28 KB, text/plain)
2001-10-01 17:17 UTC, pepijn
Details
Thread dump (10.04 KB, text/plain)
2001-10-01 17:17 UTC, pepijn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pepijn 2001-10-01 17:12:32 UTC
A short while after starting the IDE, and after succesfully opening at least one
new window, the IDE gets into a state where each new window opened is not
responsive to the mouse.

I can usually (but not always) reproduce it by for instance first opening the
project settings window, closing it, and then opening the help window, or the
other way around. I can open and close both the project settings window or the
help window any number of times, but if I then open the other window, the bug
kicks in. This is just an example, it occurs with other windows as well. I can't
discover a pattern to it, but it doesn't appear to be related to the total
number of windows open, or the number of times a new window has been opened.

The symptoms are that the system only beeps when I click any mouse button
anywhere in the window. The keyboard still works, and I can navigate around the
window and even close it by pressing Ctrl+F4. I can't switch the focus to the
window by clicking on it, and a right-mouse-button click on the task bar button
corresponding to the window doesn't yield a popup menu (but a left mouse button
click on the task bar button does switch the focus to it). The windows that were
already open continue to function normally, I can even open more windows, and
they will usually (but not always) have the same problem of the mouse not being
recognized. I can shut the application down normally.

I attach the ide.log file and a thread dump of the application with an open
project settings window that is not accepting mouse input.
Comment 1 pepijn 2001-10-01 17:17:03 UTC
Created attachment 2779 [details]
ide.log
Comment 2 pepijn 2001-10-01 17:17:41 UTC
Created attachment 2780 [details]
Thread dump
Comment 3 pepijn 2001-10-01 17:21:37 UTC
Almost the same thing happens in Forte 3.0 Community Edition, by the
way. It seems to be a bit more consistent there. I've reported this
bug to Sun as well.
Comment 4 pepijn 2001-10-01 17:58:57 UTC
Another thing I just noticed: when this bug happens, the offending
window is not listed in the Alt+Tab sequence. It's beginning to look
more and more like this is, at least partly, a JDK bug...
Comment 5 pepijn 2001-10-01 18:14:36 UTC
Aha!

It does appear to be a JDK bug, namely <A
HREF="http://developer.java.sun.com/developer/bugParade/bugs/4350698.html">this</A>
one. Apparently only a few people experience this bug but it's very
consistent for them when they do. Sun appears to be unable or
unwilling to fix it. I'm searching for a workaround...
Comment 6 pepijn 2001-10-01 18:24:51 UTC
Apologies for the HTML. The short version of that bug is: whenever you
hover your mouse over one the titlebar buttons so that the Tooltip
appears, any new windows opened after that will exhibit the behaviour
I described.

There's a user workaround: with TweakUI you can disable the 'mouse hot
tracking events' and then the bug will disappear. Apparently there's
no programmatic workaround, and Sun have closed the bug because they
can't reproduce it. Hmmmm. I'll continue investigating.
Comment 7 _ ttran 2001-10-02 07:51:55 UTC
I close this bug as WONTFIX because we really cannot fix it in the
IDE.  If you have further information please submit it to the JDK bug
database.
Comment 8 Quality Engineering 2003-07-01 16:01:26 UTC
Resolved for 3.4.x or earlier, no new info since then -> verified.

Comment 9 Quality Engineering 2003-07-01 16:39:48 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 10 Quality Engineering 2008-12-23 14:25:16 UTC
This issue had *1 votes* before move to platform component