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 20694 - Windows fail to refresh after period of non-use
Summary: Windows fail to refresh after period of non-use
Status: CLOSED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Unix
: P3 blocker (vote)
Assignee: workspaceswitcher@contrib
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-19 19:51 UTC by tnelson
Modified: 2008-12-22 09:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tnelson 2002-02-19 19:51:19 UTC 
After an extended period of non-use (overnight), when the IDE is on an inactive
virtual desktop (under the Enlightenment window manager), it will fail to
refresh when focus returns.  All I have is a big grey box (I'm in SDI mode) with
a titlebar.  I've tried minimizing/maximizing, clicking on the titlebar, using
alt-F to open the file menu, and moving the window in an attempt to get it to
refresh.  Nothing works.  I'm on a 200MHz PPro box with 128M of memory and 512M
of swap space.
Comment 1 _ tboudreau 2002-04-16 20:06:59 UTC 
This issue was misfiled against the experimental 
workspaceswitcher module.  Reassigning to core.

I use NetBeans daily on a 128Mb laptop running 
Enlightenment, and have never seen such a problem, so I'm 
marking this issue as WORKSFORME.  Please reopen it if you 
are still seeing the problem.

I have seen a situation where the JVM has crashed but the 
windows remain on the desktop.  Can you reproduce this on 
JDK 1.4, and is there any output in the console to suggest 
that the JVM has died?

Also, 128Mb and 200Mhz is a pretty minimal configuration - 
are you sure that it is not simply still pulling NetBeans 
back into memory out of the swap file? 

Some additional configuration (log file, etc.) would help 
to track down the problem.
Comment 2 Quality Engineering 2003-07-01 15:55:58 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 3 Quality Engineering 2003-07-01 16:38:14 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.