-
Bug
-
Resolution: Fixed
-
P4
-
11, 15, 16
-
b12
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8267104 | 15.0.4 | Yuri Nesterenko | P4 | Resolved | Fixed | b02 |
JDK-8260699 | 13.0.7 | Yuri Nesterenko | P4 | Resolved | Fixed | b01 |
JDK-8261068 | 13.0.6 | Yuri Nesterenko | P4 | Resolved | Fixed | b01 |
JDK-8252519 | 11.0.10-oracle | Philip Race | P4 | Resolved | Fixed | b01 |
JDK-8254123 | 11.0.9.0.1-oracle | Yasumasa Suenaga | P4 | Resolved | Fixed | b01 |
JDK-8252454 | 11.0.9 | Yasumasa Suenaga | P4 | Resolved | Fixed | b06 |
JDK-8252959 | 11.0.8.0.4-oracle | Yasumasa Suenaga | P4 | Closed | Fixed | master |
I investigated it, then I found out current implementation cannot handle default charset.
If charset is set to UTF-8, it would be handled as "DEFAULT_CHARSET" in WFontConfiguration::initTables. However it does not affect native font name, so we cannot find valid font.
- backported by
-
JDK-8252454 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Resolved
-
JDK-8252519 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Resolved
-
JDK-8254123 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Resolved
-
JDK-8260699 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Resolved
-
JDK-8261068 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Resolved
-
JDK-8267104 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Resolved
-
JDK-8252959 JFrame::setVisible crashed with -Dfile.encoding=UTF-8 on Japanese Windows.
- Closed
- links to
-
Commit openjdk/jdk13u-dev/7a3ce726
-
Commit openjdk/jdk15u-dev/30458d46
-
Review openjdk/jdk13u-dev/100
-
Review openjdk/jdk15u-dev/55