I apologize in advance if this question should be located elsewhere in the forum, or if this problem has already been addressed and my attempts to search for it have failed.
I am part of a team that is developing a platform application using the Netbeans 6.8 Platform. Our program has a known issue where, on certain computers, the program will lock-up or otherwise chew through resources upon being restored.
In general, the problem presents itself sporadically. It appears to happen most often when the application has been minimized, the user goes to work in other programs, and then returns to the application. There seems to be no correlation between what the application is currently doing and how often the problem occurs.
Upon the restore from minimized state, multiple things have happened: the application has rendered briefly, then gone completely black; the application fails to render altogether, but parts will appear upon mouseover; a dialog from the application will appear, but once addressed, will not dissappear.
The problem also has varying effects on the processing state of the computer, sometimes only the application is affected. Sometimes, the application and the IDE will become unresponsive. And in some cases, the entire computer locks-up, preventing even the task manager from being launched. On occassion, the application will recover from this state, but most times it will not. When the task manager can be launched, it appears that the process running the application generally takes more than 50% cpu power.
About the application: It is multi-threaded, multi-windowed (using TopComponent), and makes a number of network calls in addition to managing the user interface. We have been unable to make a connection between any of these windows being open and the problem occuring.
The problem has occurred on three machines, an XP 64-bit 2GHz 8GB RAM Dell machine (experienced complete computer lockup), an XP 64-bit 2GHz dual-core Dell laptop (locked-up with dialog but Netbeans IDE recovered), and a Windows 7 64-bit 2.8GHz dual core Dell laptop (experiences the problem most often). A fourth machine has never seen the problem, Windows 7 64-bit 2.67Ghz quad-core 4GB RAM.
The problem has occurred from within the IDE in both Run and Debug mode, and outside of the IDE as a zip distribution.
It is hard to replicate this issue, and no method we have tried yet can do so reliably. I appreciate any help or insight that can be given.
I sorted this by creating a tiny window (temporarily) in the corner of the screen that appeared for 1 second, every few minutes and also load the file i/o to create a temp file on disk at the same time.
I have since left Netbeans apps minimised for over 2 hours now and they come back to life with no problems.
This is the class I produced to do the work. You need to pass it the encapsulating frame to recognise when it is minimised or restored.
public void loadFunction()
Date date = new Date();
long time = date.getTime();
long period = time - ticks;
period /= 1000;// seconds
period /= 60; // minutes.
String timeStr = format.format(date);
String minStr = "Costing : minimised for ... " + period + " mins @ " + timeStr;