.so files in ~/.jdks/ja-25 with debug info and not stripped ?

[bubbleguuum]

None of the files in ~/.jdks/ja-25 are stripped and contain debug info.

Biggest offender is libjvm.so at 733 MB:

~> du ~/.jdks/ja-25/lib/server/libjvm.so 
733M	/<redacted>/.jdks/ja-25/lib/server/libjvm.so

~> file ~/.jdks/ja-25/lib/server/libjvm.so
/<redacted>/.jdks/ja-25/lib/server/libjvm.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=45bcf71518ae7eaf215b5c9b044a0fd64c29db70, with debug_info, not stripped, too many notes (256)

Once stripped (strip -s) it is a more reasonable 24 MB.

Other .so libs in ~/.jdks/ja-25/lib are not stripped either.

This results in gigantic images generated with ja install and ja tool jlink. And the ja installation (~/.jdks/ja-25) being unnecessarily huge (1.4 GB).

[DanielThomas]

Our installation script just uses jlink to create the image, so the JDK that was on JAVA_HOME or PATH that we linked from must have been unstripped.

[bubbleguuum]

Thank you for your answer that put me on the right track to understand this issue.

I use openSUSE Tumbleweed and Java 25 from its stock java-25-openjdk package was used to generate the ja install. For some reason, its jmods (shipped as separate jmod files) have debug info and are unstripped (while the rest of the JDK is not). Will check with openSUSE if that is intended, but it doubt it was.

[bubbleguuum]

Indeed quite a snafu in the packaging:

https://bugzilla.opensuse.org/show_bug.cgi?id=1282358

[bubbleguuum]

Note that invoking jlink with --strip-debug in install.sh (Line 328) would fix this issue:

https://inside.java/2019/10/02/strippingdebug-jlink/

I would have submitted a PR had it been possible.