Closed wuzhengxuan closed 2 months ago
I am add the -DhprofStrictnessWarning=true in JVM params,it does't wrok.
It worked in MAT 1.15 on my PC. Can you update the eclipse-mat-deps to 1.15?
Hi @wuzhengxuan From the error message, the dump is incomplete or has some wrong data, so even if MAT 1.15 can parse it, there may be some wrong analysis results.
You can update the mat version locally by modifying the following line:
You can update the mat version locally by modifying the following line:
Thanks, I'm try to update it.Does org.eclipse.osgi need to be updated?
I'm try to update it.Does org.eclipse.osgi need to be updated?
You can update the mat version locally by modifying the following line:
Hi,@D-D-H,I'm update the https://download.eclipse.org/mat/1.14.0/update-site/ to 1.15.0,the project can build,but analysis the hprof file has error:java.lang.NoSuchMethodError: 'java.lang.String org.eclipse.mat.hprof.ui.HprofPreferences.methodsAsClasses()'.How to fix it?Thanks.
I suspect it's an issue with the ClassLoader, which did not load the heap-dump module hook org.eclipse.mat.hprof.ui.HprofPreferences. Now I don't know how to fix it。
After upgrading Jifa to MAT 1.15, it still doesn't work. I found that the local MAT 1.15 had Parser Strictness set to 'warn', so it could open the file. It is indeed a file error issue as you mentioned. However, what's strange is that the .hprof file can be opened normally in strict mode, but after compressing it to .gz, it cannot be opened. I will try to submit an issue to MAT. Thank you.
error: org.eclipse.jifa.hda.api.AnalysisException: org.eclipse.mat.SnapshotException: The HPROF parser encountered a violation of the HPROF specification that it could not safely handle. This could be due to file truncation or a bug in the JVM. Please consider filing a bug at eclipse.org. To continue parsing the dump anyway, you can use -DhprofStrictnessWarning=true or set the strictness mode under Preferences > HPROF Parser > Parser Strictness. See the inner exception for details.
add the -DhprofStrictnessWarning=true in JVM params?