-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b105
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8214608 | 8u211 | Paul Hohensee | P3 | Resolved | Fixed | b01 |
| JDK-8209948 | 8u202 | Paul Hohensee | P3 | Resolved | Fixed | b01 |
| JDK-8220861 | emb-8u211 | Paul Hohensee | P3 | Resolved | Fixed | master |
I encountered JVM crash when I passed -XX:+EnableTracing.
I checked core image, it crashed in EventBooleanFlagChanged::writeEvent()
which is called by Arguments::apply_ergo() because thread had not been
initialized. (JVM seems to log changing GC algorithm to G1.)
writeEvent() uses ResourceMark. Default constructor of ResourceMark uses
ResourceArea in current thread. So ResourceMark in writeEvent() should
pass valid ResourceArea.
I checked core image, it crashed in EventBooleanFlagChanged::writeEvent()
which is called by Arguments::apply_ergo() because thread had not been
initialized. (JVM seems to log changing GC algorithm to G1.)
writeEvent() uses ResourceMark. Default constructor of ResourceMark uses
ResourceArea in current thread. So ResourceMark in writeEvent() should
pass valid ResourceArea.
- backported by
-
JDK-8209948 JVM crashes with -XX:+EnableTracing
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- duplicates
-
-
- Closed
-