In the following we use "crash" to mean an uncaught exception which triggers a "crash report" dialog in jGRASP. This may or may not be a real problem - many uncaught exceptions do not cause any harm.
Sun bug 6672017 is now affecting XP as well as Vista. Our existing work-around will now be applied on XP.
Using the Java debugger on files not compiled in debug mode may cause a crash.
Choosing a very small or oddly proportioned font may cause a crash.
Interactions treats boolean '&' expressions as if they were '|'.
Opening a structure identifier viewer on a partially-constructed hash table may cause a crash.
The structure identifier viewer is chosen by default even when all mappings to known structures have low confidence.
Newer versions of Cygwin that have the "alternatives" system implemented don't work with the included C, C++, and Objective-C compiler environments.
Arguments in the "Run Arguments" bar are processed for variables in the same way as Run arguments in the settings, so that % must be escaped as %%. This was not our intention and the arguments in the "Run Arguments" bar will no longer support variables or require percent signs to be escaped.
The file browser is sometimes very slow, especially immediately after a compile or run action (jGRASP may appear frozen for a few seconds after a compile or run).
Choosing a very small font scale and CSD font size may cause jGRASP to crash, and it will continue to crash each time it is restarted (it will become unusable).
Control panel may get stuck as always-on-top due to Sun bug 6829546 for Java 1.6.0_16. Our previous work-around cut out at 1.6.0_16 because we assumed Sun would have fixed this by then. The work-around will now apply to all 1.6.0_12 and higher until the bug is known to be fixed.
Clicking and dragging or entering text in the (very small) selection area for an empty debug eval value when the debugger is not running will cause a crash.
Copy-and-paste of debugger values using Ctrl-C produces a useless result. In 1.8.7_02 it will produce the text shown for the value in the tree. This also applies to items in the debugger threads tree.
Clicking the "invoke method" button in a viewer before the viewer has initialized will cause a crash.
Crashes due to Sun bug 6828938, which happen frequently, are now ignored.
Tools plugin toolbar items will appear when an editing window is taken out of the virtual desktop, even if the associated tools are not installed. Clicking on such a toolbar item can cause a crash.
Folding using selection and the keyboard or by mouse clicking when the CSD diagram has been edited may cause a crash.
The "Clear Workbench" item on the workbench menu is not grayed out when the workbench is not running, and using it when the workbench is not running will cause a crash.
CSD generation on code that has multiple statments or major code segments on one line may cause a crash.
An "interactions" pane has been added.
Control panel may get stuck as always-on-top due to Sun bug 6829546.
Postscript printing will fail on some non-Windows systems due to Sun bug 6633656.
On 32-bit Windows, when a specific Java version is selected through jGRASP startup settings, jGRASP icons will group with other Java icons on the Windows taskbar instead of in their own group.
Native printing on non-Windows systems now uses PrintService-based PostScript printing rather than a call to lpr, which allows an easy choice of printer and some printer properties.
jGRASP may not locate the Java compiler and the Java debugger may not work under 64-bit Windows if an appropriate 32-bit version of Java is not installed. This is fixed, but some minor problems when running under 64-bit Java remain.
PostScript printing with a line spacing other than 1.0 will leave horizontal gaps in the CSD.
Using "Run to Cursor" in the Java debugger when the cursor is on an unloaded class will not work, and if a breakpoint is encountered it will cause a crash.
Hovering the mouse over a bad URL link in the jGRASP Help/Documentation browser will cause a crash.
Entering a new eval expression in the Java debugger while the current thread is running will cause a crash.
When running under Java 1.5.x, if the Java debugger fails to attach after ten seconds, a crash will be reported in addition to a useful error message.
Work-arounds and warnings for numerous Java bugs were added.
Clicking the mouse and dragging in an empty bookmarks or workspaces list will cause a crash.
jGRASP may lock up when a file chooser dialog is opened under Java 1.6.0_10 rc (6u10 rc) due to a Java bug.
There are various layout and color problems with the Nimbus Look&Feel, some due to Nimbus/Synth bugs, some due to jGRASP bugs.
Using "Run as Applet" or "Debug as Applet" from an unnamed file will cause a crash.
The java.util.LinkedList presentation viewer will fail (display a viewer exception) when all items don't fit in the window and the view is scrolled all the way to the right.
Font size will be zero for all gui elements on Mac OS X under Java 1.6 with Metal or Motif L&F on systems with resolution higher than 96 dpi, making jGRASP unusable.
If a J2ME project has items in the jGRASP CLASSPATH settings, the preverify action will cause a crash.
Font size will be zero for all gui elements on Mac OS X under Java 1.6 with Metal or Motif L&F on systems with resolution higher than 96 dpi, making jGRASP unusable.
If a J2ME project has items in the jGRASP CLASSPATH settings, the preverify action will cause a crash.
When using the system "Quit" function on Mac OS X, if edited files are open and the user chooses to cancel the quit operation, jGRASP will be killed and changes will be lost.
Maximized windows on virtual desktop don't resize correctly on many systems.
Startup script will fail on unknown systems (anything other than Windows, Mac OS X, Intel Linux, and SPARC Solaris), and may fail on other systems.
Pasted test from some rtf sources, such as MS Word 2007, will include some rtf commands.
Java debugger may not work when jGRASP is started from the bin/jgrasp script on Ubuntu, and possibly other Linux and UNIX systems.
Maximized windows on the virtual desktop are too tall on some versions of OS X for some versions of Java.