-
Bug
-
Resolution: Fixed
-
P2
-
13
-
b02
-
arm
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8236180 | 14 | Aleksei Voitylov | P2 | Resolved | Fixed | b28 |
according to Craig Condit:
It appears there is some sort of regression in serviceThread.cpp which consumes all available CPU on jdk13 arm32 builds (tested on multiple vendor builds including AdoptOpenJDK and BellSoft). This is easily reproducible -- I used multiple Raspberry Pis (2 and 3).
All java processes consume 100% of a core in "Service Thread". To reproduce, launch any long-running java process (such as jshell), and in another terminal, run "top -H" to view CPU usage by thread.
This does not occur on jdk 11 or jdk 12.
It appears there is some sort of regression in serviceThread.cpp which consumes all available CPU on jdk13 arm32 builds (tested on multiple vendor builds including AdoptOpenJDK and BellSoft). This is easily reproducible -- I used multiple Raspberry Pis (2 and 3).
All java processes consume 100% of a core in "Service Thread". To reproduce, launch any long-running java process (such as jshell), and in another terminal, run "top -H" to view CPU usage by thread.
This does not occur on jdk 11 or jdk 12.
- backported by
-
JDK-8236180 100% cpu on arm32 in Service Thread
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Resolved
-