This is a followup to JDK-8328944, which addressed some cases where mtNone showed up in reports, but there is more to do here.
Here we mainly concentrate on removing the default parameter, so that no-one is tempted to use the APIs without providing the mem tag, if known.
Here we mainly concentrate on removing the default parameter, so that no-one is tempted to use the APIs without providing the mem tag, if known.
- causes
-
JDK-8356020 Failed assert in virtualMemoryTracker.cpp
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- clones
-
JDK-8344883 Force clients to explicitly pass mem_tag value, even if it is mtNone
-
- Resolved
-
- is cloned by
-
-
- Closed
-
- links to
-
Commit(master)
openjdk/jdk/9a2a2c5b
-
Review(master)
openjdk/jdk/24634
(2 links to)