Details
-
Bug
-
Resolution: Fixed
-
P2
-
7u72, 8, 9
-
b43
-
Verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8084716 | emb-9 | Daniel Fuchs | P2 | Resolved | Fixed | team |
JDK-8068109 | 8u45 | Daniel Fuchs | P2 | Resolved | Fixed | b02 |
JDK-8066907 | 8u40 | Daniel Fuchs | P2 | Closed | Fixed | b19 |
JDK-8069974 | emb-8u47 | Daniel Fuchs | P2 | Resolved | Fixed | team |
JDK-8071323 | 7u85 | Daniel Fuchs | P2 | Resolved | Fixed | b01 |
JDK-8071612 | 7u80 | Daniel Fuchs | P2 | Resolved | Fixed | b07 |
JDK-8071593 | 7u79 | Daniel Fuchs | P2 | Closed | Fixed | b07 |
Description
The traces show that LogManager.getUserContext() calls JavaAWTAccess - and henceforth AppContext.getAppContex() from within a synchronized block - when in fact it could be called before entering the critical section.
Note: This change is not sufficient to completely remove the deadlock: if the LogManager has not been initialized yet, then ensureLogManagerInitialized will end up calling LogManager.getUserContext() from within another critical section, with potentially the same effect. In this second case removing this second critical section is not an option.
Attachments
Issue Links
- backported by
-
JDK-8068109 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Resolved
-
-
JDK-8069974 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Resolved
-
-
JDK-8071323 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Resolved
-
-
JDK-8071612 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Resolved
-
-
JDK-8084716 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Resolved
-
-
JDK-8066907 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Closed
-
-
JDK-8071593 LogManager unecessarily calls JavaAWTAccess from within a critical section
-
- Closed
-
- blocks
-
JDK-8065709 Deadlock in awt/logging apparently introduced by 8019623
-
- Resolved
-
- relates to
-
JDK-8065709 Deadlock in awt/logging apparently introduced by 8019623
-
- Resolved
-
-
JDK-8071591 [TESTBUG] java/util/logging/LogManagerAppContextDeadlock.java test started to fail due to JDK-8065991
-
- Resolved
-
-
JDK-8019623 Lack of synchronization in AppContext.getAppContext()
-
- Resolved
-