OpenJDK / amber / amber
changeset 60310:2fc917015437
8240534: Shenandoah: ditch debug safepoint timeout adjustment
Reviewed-by: rkennke
| author | shade |
|---|---|
| date | Wed, 04 Mar 2020 19:23:13 +0100 |
| parents | 707abe6ca3cb |
| children | d0b769130118 |
| files | src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp |
| diffstat | 1 files changed, 0 insertions(+), 10 deletions(-) [+] |
line wrap: on
line diff
--- a/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp Wed Mar 04 14:55:43 2020 +0100 +++ b/src/hotspot/share/gc/shenandoah/shenandoahArguments.cpp Wed Mar 04 19:23:13 2020 +0100 @@ -191,16 +191,6 @@ if (FLAG_IS_DEFAULT(TLABAllocationWeight)) { FLAG_SET_DEFAULT(TLABAllocationWeight, 90); } - - // Make sure safepoint deadlocks are failing predictably. This sets up VM to report - // fatal error after 10 seconds of wait for safepoint syncronization (not the VM - // operation itself). There is no good reason why Shenandoah would spend that - // much time synchronizing. -#ifdef ASSERT - FLAG_SET_DEFAULT(SafepointTimeout, true); - FLAG_SET_DEFAULT(SafepointTimeoutDelay, 10000); - FLAG_SET_DEFAULT(AbortVMOnSafepointTimeout, true); -#endif } size_t ShenandoahArguments::conservative_max_heap_alignment() {