-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
jenkins version: 2.138.4
p4 plugin version: 1.9.6
Hi,
When after upgrade the p4-plugin from 1.8.4 to 1.9.6, we found a lot of String: "MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction'" apears in the dump heap with a GC root to hudson.model.Hudson, and cannot be released in a short time, which results in a dramatically heap size increasement (There are many jobs use p4-plugin in our jenkins).
Compared with p4-plguin 1.8.4 and 1.9.6, the field 'charset' in org.jenkinsci.plugins.p4.tagging.TagAction was removed. Do you have any ideas how to stop generating MissingFieldException: No field 'charset' found in class 'org.jenkinsci.plugins.p4.tagging.TagAction' everywhere? Thanks a lot
<- extra - class: hudson.diagnosis.OldDataMonitor$VersionRange, value: java.lang.String #2508149 <- val - class: java.util.concurrent.ConcurrentHashMap$Node, value: hudson.diagnosis.OldDataMonitor$VersionRange #84934 <- next - class: java.util.concurrent.ConcurrentHashMap$Node, value: java.util.concurrent.ConcurrentHashMap$Node #717387 <- next - class: java.util.concurrent.ConcurrentHashMap$Node, value: java.util.concurrent.ConcurrentHashMap$Node #645817 <- [458830] - class: java.util.concurrent.ConcurrentHashMap$Node[], value: java.util.concurrent.ConcurrentHashMap$Node #612859 <- table - class: java.util.concurrent.ConcurrentHashMap, value: java.util.concurrent.ConcurrentHashMap$Node[] #3166 <- data - class: hudson.diagnosis.OldDataMonitor, value: java.util.concurrent.ConcurrentHashMap #5263 <- instance - class: hudson.ExtensionComponent, value: hudson.diagnosis.OldDataMonitor #1 <- [5] - class: java.lang.Object[], value: hudson.ExtensionComponent #1661 <- elementData - class: java.util.ArrayList, value: java.lang.Object[] #212994 <- extensions - class: hudson.ExtensionList, value: java.util.ArrayList #245755 <- administrativeMonitors (Java frame) - class: hudson.model.Hudson, value: hudson.ExtensionList #1
Hi robby_he - Thanks for highlighting this.
Have you already been to 'Manage Jenkins' and tried to clear out old data?
If you have not and that option is available, please make sure you have backed up your jobs then try clearing out the old data. Does this solve the problem?