-
Enhancement
-
Resolution: Fixed
-
P3
-
1.4.2
-
None
-
mantis
-
x86
-
windows_xp
Plugging all the problems described in bug
4482430:Unexpected exception from NativeFontWrapper.registerFonts(Native Method)
will take some time, as the full set of problems can't yet be identified.
A useful measure is to prevent the situation occurring in the most common
cases by identifying at installation time the fonts that may cause this kind
of crash. Installation time is preferred because it expensive to do tests at
run time, and in some cases they may be more likely to cause a crash than
prevent one.
The targetted platform is win32. win64 is a developer release and the
linux and solaris platforms have not yet been causing problems like this.
4482430:Unexpected exception from NativeFontWrapper.registerFonts(Native Method)
will take some time, as the full set of problems can't yet be identified.
A useful measure is to prevent the situation occurring in the most common
cases by identifying at installation time the fonts that may cause this kind
of crash. Installation time is preferred because it expensive to do tests at
run time, and in some cases they may be more likely to cause a crash than
prevent one.
The targetted platform is win32. win64 is a developer release and the
linux and solaris platforms have not yet been causing problems like this.
- relates to
-
JDK-4482430 Unexpected exception from NativeFontWrapper.registerFonts(Native Method)
-
- Resolved
-
-
JDK-4755476 RFE: JRE win32 install time support for identifying bad fonts.
-
- Closed
-