-
Bug
-
Resolution: Fixed
-
P4
-
25
-
b08
-
generic
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8350798 | 24.0.2 | Dhamoder Nalla | P4 | Resolved | Fixed | b01 |
JDK-8351358 | 21.0.8 | Dhamoder Nalla | P4 | Resolved | Fixed | master |
Host: AMD Ryzen 5 2600 Six-Core Processor , 12 cores, 15G, Windows 11 , 64 bit Build 22621 (10.0.22621.3958)
Time: Tue Dec 10 16:32:49 2024 K��-eur t鬩 idBuild 22621 (10.0.22621.3958) elapsed time: 1272.020845 seconds (0d 0h 21m 12s)
Typically, the timezone is replaced with random junk, followed by leftovers of the OS version string. Interestingly, the junk remains consistent across multiple machines.
- backported by
-
JDK-8350798 Corrupted timezone string in JVM crash log
-
- Resolved
-
-
JDK-8351358 Corrupted timezone string in JVM crash log
-
- Resolved
-
- relates to
-
JDK-8340465 Timezone printed in hs_err file is corrupt on Windows
-
- Open
-
- links to
-
Commit(master) openjdk/jdk21u-dev/d29111af
-
Commit(master) openjdk/jdk24u/114f2e34
-
Commit(master) openjdk/jdk/2bef5b4a
-
Review(master) openjdk/jdk21u-dev/1382
-
Review(master) openjdk/jdk24u/93
-
Review(master) openjdk/jdk/23246