Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8264411: serviceability/jvmti/HeapMonitor tests intermittently fail due to large TLAB size #3265

Closed
wants to merge 4 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -166,13 +166,13 @@ public static int[][][] sampleEverything() {

// Trigger GC then loop around an allocation loop and wait until Object Sampling
// is enabled for every later allocation. It takes two steps:
// 1. Consume current TLAB, whose size can be varies with heap/GC configuration
// 1. Consume current TLAB, whose size can vary with heap/GC configuration
// 2. Consume initial ThreadHeapSampler::_bytes_until_sample, which is around 512KB
//
// Step1 trigger GC to consume current TLAB
System.gc();
// Step2 loop allocation consume "bytes until sample", each iteration allocate
// about 1600KB, 10 iterations can definitly consume initial "bytes until sample"
// Step2 loop allocation consumes "bytes until sample", each iteration allocates
// about 1600KB, so 10 iterations will definitly consume initial "bytes until sample"
final int maxTries = 10;
int[][][] result = new int[maxTries][][];
for (int i = 0; i < maxTries; i++) {