-
Bug
-
Resolution: Fixed
-
P3
-
7u85
-
b94
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8149215 | 8u101 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-8142401 | 8u92 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-8144640 | 8u91 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-8141282 | 8u72 | Shafi Ahmad | P3 | Resolved | Fixed | b09 |
JDK-8155311 | emb-8u101 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-8147160 | emb-8u91 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-8142478 | 7u101 | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b01 |
JDK-8141283 | 7u95 | Shafi Ahmad | P3 | Resolved | Fixed | b09 |
2. Only statement inside VM_Version_Ext::resolve_cpu_information_details which may cause 'Floating point exception' is "_no_of_packages = _no_of_threads / threads_per_package"
when 'threads_per_package' is zero.
3. Point (2) implies either 'threads_per_core()' or 'cores_per_cpu()' evaluate to zero.
4. From the implementation of function 'cores_per_cpu()' it is obvious minimum value return by this function is 1, where as threads_per_core() may evaluated to zero.
So the quick fix is fall back to a default value if we get threads_per_core '0', so that we don't crash.
- backported by
-
JDK-8141282 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8141283 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8142401 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8142478 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8144640 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8147160 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8149215 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-
-
JDK-8155311 JVM Crashing During startUp If Flight Recording is enabled
-
- Resolved
-