JDK-6400685 : Font2DTest.jar is failing for Arabic-Majalla UI on Windows-Vista
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 1.1.6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_vista
  • CPU: x86
  • Submitted: 2006-03-20
  • Updated: 2011-12-22
  • Resolved: 2006-04-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
5.0u8Fixed 6 b81Fixed
Related Reports
Relates :  
JDK-4924220 - Microsoft Sans Serif (True Type) font is not rendered properly
Relates :  
JDK-6282527 - LCD text artifacts due to T2K (font rasteriser) scan conversion of contour to glyph image.
Description
JDK build used:jdk-6-beta2-bin-b75-windows-i586-09_mar_2006.exe
               jdk-6-beta2-bin-b75-windows-amd64-09_mar_2006.exe

Locale:ar_SA.
OS:widows-Vista beta1(build 5308)
Arc:AMD64/x86.

Reproducable steps
===================
1)Installed the jdk bundles
2)set the JAVA_HOME and PATH
3)goto java home directory under that /demo/jfc/Font2DTest.jar
4)run the following command java -jar Font2DTest.jar.
5)choose the unicode range as Arabic and set the font as majalla UI,
JVM crashed and detected unexpected error
Please see the attached log file:hs_err_pid1160.log

Note:
=====
- jvm crashing is for majalla UI - Arabic only.for other fonts there were no issues.
- Reproducable on both 32bit/64-bit Vista.
Comments
EVALUATION Problem is sideeffect of support for smart dropout control that was added as part of fix for 6282527. In smart dropout mode we use new data format for storing ON and OFF transitions (during scan conversion) thats packs transition line number and fractional offset. However, in case of very small thin glyph we are altering these arrays outside of sc_mark to ensure at least 1 pixel is filled. This code was not updated to support new data format. This could cause incorect offset values read at actual dropout processing stage and lead to crash. We need to update code that handle this special case to support new data format for transitions arrays.
21-03-2006
EVALUATION The crash is in the T2K rasteriser and is reproducible if you have the font on XP, but I could not reproduce it on Solaris. This appears to have been introduced in b51 along with the fix for 6282527/4924220 Also the bug is not reproducible on 1.5.0_06 but is reproducible on 1.5.0_07 which has the backport of this same fix.
20-03-2006