This chapter lists high-visibility bugs that have been addressed in this release. It is not a complete listing of all of the bugs addressed. If you still have issues with any of these bugs, please file a new bug at http://bugreport.apple.com/ under the Java (new bugs)
component, version X
. Refer to the bug number indicated below in your new bug if you believe it is the same issue.
Java Applets
Java Application Support
Java AWT
Java Events
Java Graphics
Java Input Methods
Java Libraries
Java Printing
Java SWT Support
Java Virtual Machine
Java Web Start
Other Resolved Issues
Default applet memory limits too low
The default maximum heap size for Java applets was set to 64 MB in Java 1.4.2 and J2SE 5.0. This is inconsistent with other platforms and often not enough for memory-hungry applets.
The default maximum heap size for applets is now 96 MB in Java 1.4.2 and J2SE 5.0.
Previous Java application stub incompatibilities
The Java application stub shipped with J2SE 5.0 Release 4 and various Intel-based Macs requires Mac OS X 10.3.9 or later to run.
A new Java application stub is included with Java for Mac OS X v10.4 Release 5. This stub is Universal (supports both PowerPC and Intel-based Macs) and is compatible with Mac OS X v10.2 and later for Java 1.4.2 applications. This stub also fixes launch issues on Mac OS X v10.3 with QuickTime 7.0.4 and later installed. To use the latest stub, either repackage your application with Jar Bundler or swap your application’s stub with the one found in /System/Library/Frameworks/JavaVM.framework/Resources/MacOS/
.
Note: On Intel-based Macs, applications that set JVMVersion
to 1.3*
and use the new Java application stub are provided J2SE 5.0 as their Java runtime.
Transparent window dragging
Window made transparent via setBackgroundColor
couldn’t be dragged.
Use a boolean value with the apple.awt.draggableWindowBackground
per-window client property to control if a window can be moved by dragging its background.
Dead keys reported incorrectly
Dead key combinations, such as Option-E and Option-U, were reported as a key event with no key code or key character.
Pressing a dead key combination generates the correct code, such as VK_DEAD_GRAVE
, VK_DEAD_ACUTE
, or VK_DEAD_CIRCUMFLEX
, for that combination.
Incorrect synchronization
A race condition in the clean-up of drawable delegates for native peers could result in a crash.
The clean-up of drawable delegates for native peers is now synchronized correctly.
Erroneous Input Method Events
Components that were not prepared to respond to input method events received them, which caused the AWT to bring up an input window.
Components that return null
from the getInputMethodRequests
method no longer receive input method events.
Multiple characters generated by one key stroke
If a component didn't support input method events and a key combination resulting in multiple characters was entered, the component only received one KEY_TYPED
event for the first character generated by the event.
Entering a key combination that results in multiple characters now generates a KEY_TYPED
event for each character generated.
Daylight Saving Time adjustment
Beginning in 2007, Daylight Saving Time in the United States starts three weeks earlier (March 11, 2007) and ends one week later (November 4, 2007).
Java for Mac OS X v.10.4 Release 5 includes new time zone files that handle the recent changes to Daylight Saving Time. The included files are current as of January 8, 2007.
Print service lookup returns null results
When contact with a printer could not be established, PrintServiceLookup.lookupPrintServices
may have returned an array of PrintServices
objects that contained null
entries.
Printers that cannot be contacted are no longer added to the available printers list. Also, the array returned by PrintServiceLookup.lookupPrintServices
only contains valid PrintService
objects.
Printer changes ignored
Changing the printer in a javax.print
print dialog was sometimes ignored, causing print jobs to route to the default printer.
All print jobs go to the printer specified using the javax.print
print dialog.
SWT embedding
Support for embedding AWT frames into an SWT-based application required a separate download.
The SWT embedding patches are included with Java for Mac OS X v.10.4 Release 5. The patches require Eclipse 3.2RC3 and later. See the Package org.eclipse.swt.awt documentation for more information on SWT AWT embedding support.
AWT frames embedded in SWT composites
AWT embedded frames would not appear when you created a Composite, set its size, and then added the embedded AWT frame.
Embedded frames always appear, regardless of the size of the parent Composite at creation time.
Crashes when embedding AWT Frames in SWT Shells
Embedding an AWT Frame in an SWT Shell caused crashes shortly after the shell appeared.
Embedding an AWT Frame within an SWT Shell no longer causes crashes. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=171105 for more information.
Crashes when embedding AWT Frames in SWT Shells after using SWT Browsers
An SWT-based application crashed if the application used an SWT Browser before embedding an AWT Frame in an SWT Shell.
Embedding an AWT Frame after using an SWT Browser no longer causes crashes. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=163629 for more information.
Crashes when closing embedded AWT Frames
SWT-based applications crashed after disposing of an embedded AWT Frame and then continuing to work with the window.
Closing an embedded AWT Frame and then working with its window no longer causes crashes. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=162687 for more information.
Concurrent Mark Sweep Garbage Collection Issues
Applications that use the +UseConcMarkSweepGC
flag (Concurrent Mark Sweep Garbage Collection algorithm) were often unstable.
Applications that use the +UseConcMarkSweepGC
algorithm execute properly.
Crashes when using the -server option
In some situations, running applications using the C2 compiler (-server
) on Intel-based Macs crashed during Just-in-time compilation.
The C2 compiler on Intel-based Macs is considerably more reliable in this release.
Java Cache Viewer crash
Java Cache Viewer crashed if the icon
element’s name
attribute in a JNLP file did not have a file extension.
Java Cache Viewer accepts any file name for icon elements.
JNLP applications use incorrect version of Java Web Start
JNLP-based applications that use Java 1.4.2 or 1.3.1 were started with a different version of Java Web Start than J2SE 5.0 JNLP-based applications. This caused caching issues and other behavioral issues between versions.
All JNLP applications are launched using the Java Web Start version installed by J2SE 5.0 using the Java Virtual Machine requested by the JNLP file.
Table 1-1 lists numerous issues present in previous versions of Java for Mac OS X that are resolved in Java for Mac OS X v10.4 Release 5.
Radar # | Description |
---|---|
4691177 | AWT crash with VoiceOver or Access for Assistive Devices |
4360526 | Crash when passing |
4564214 |
|
4327495 | Spurious warning: |
4517104 | Incorrect manipulation of images with type |
4531188 | Null Pointer Exception in |
4582048 | Problems drawing a dotted rectangle using |
4915077 |
|
4739661 |
|
4769872 | Extraneous |
4872807 | Crash when drawing text into a window that is being disposed |
4814231 | Untested exception when using |
4826541 | Memory leak in JNI |
4851158 | Untested trap when using with |
4900738 |
|
4738148 | Root certificates updated to match certificates included with Mac OS X v.10.4.8 |
© 2007 Apple Inc. All Rights Reserved. (Last updated: 2007-03-08)