Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 23
Affects Version/s: 23
Component/s: hotspot
Labels:
- diagnostics
- footprint

Subcomponent:
compiler
Resolved In Build:
b21

As discussed in [1], we'd like to introduce a default memory limit for debug builds of the JVM. That way, we can catch pathological compiler errors that have unreasonably high memory footprint as one of their symptoms early during testing.

[1] https://mail.openjdk.org/pipermail/hotspot-compiler-dev/2024-April/074787.html

is blocked by

JDK-8331344 No compiler replay file with CompilerCommand MemLimit

Resolved

relates to

JDK-8332537 C2: High memory usage reported for compiler/loopopts/superword/TestAlignVectorFuzzer.java

Resolved

JDK-8333258 C2: high memory usage in PhaseCFG::insert_anti_dependences()

Resolved

JDK-8333697 C2: Hit MemLimit in PhaseCFG::global_code_motion

Closed

JDK-8318016 Per-compilation memory ceiling

Resolved

JDK-8331283 [AArch64] C2: Register Allocator uses > 1GB in compiler/c2/TestFindNode.java

Open

JDK-8337821 C2: Hit MemLimit in PhaseChaitin::Split in VectorReplicateLongSpecialImmTest.java

Open

JDK-8331295 C2: Do not clone address computations that are indirect memory input to at least one load/store

Closed

JDK-8343038 C2: TestScalarReplacementMaxLiveNodes.java fails with fatal error: Hit MemLimit in escape analysis

Closed

links to

Commit openjdk/jdk/ad78b7fa

Review openjdk/jdk/18969

(4 relates to, 2 links to)

Assignee:: Thomas Stuefe

Reporter:: Thomas Stuefe

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2024-04-26 02:54

Updated:: 2024-11-11 05:45

Resolved:: 2024-05-08 03:41

Details

Description

Attachments

Issue Links

Activity

People

Dates