[GR-73296][Native Image] ClassCastException: HostedInterface cannot be cast to HostedInstanceClass

[codesimplicity]

Describe the Issue

We have multiple Spring Boot applications which we build via the Gradle task bootBuildImage using paketobuildpacks/oracle:latest (GraalVM 25).
We also apply a PGO profile which we regularly generate for each application.

When trying to update to Spring Boot 3.5.10, this build reproducibly fails for one of our applications while it works for others.

Details:

• fails with PGO profile generated with Spring Boot 3.5.9
• works with PGO profile generated with Spring Boot 3.5.10
• works without PGO profile

The builds run on GitHub action runners. I can reproduce it on a system with the details in "Operating System and Version".

My assumption would be that any PGO profile can be used in a build. The only downside may be optimising for the wrong things. That's at least how I read the documentation.

Using the latest version of GraalVM can resolve many issues.

• I tried with the latest version of GraalVM.

GraalVM Version

paketobuildpacks/oracle:latest (GraalVM 25)

Operating System and Version

Linux gh-action-runner 5.14.0-611.13.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Dec 12 11:55:11 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Build Command

./gradlew build bootBuildImage -PimageName=some-application:TEMP-PR_157

config in build.gradle:

def iprofFile = "service.iprof"
bootBuildImage {
    def nativeImageBuildArguments = "-J-Xmx20G -H:IncludeLocales=de,en"
    if (project.hasProperty('buildInstrumentedImage')) {
        nativeImageBuildArguments += project.buildInstrumentedImage ? " --pgo-instrument " : ""
    } else if (new File(iprofFile).exists()) {
        nativeImageBuildArguments += " --pgo=/workspace/BOOT-INF/classes/${iprofFile}"
    }

    imageName = project.hasProperty("imageName") ? project.ext.imageName : null
    // default misses 'libstdc++.so.6' and may also not work with Kubernetes mounts
    // see https://docs.spring.io/spring-boot/how-to/native-image/developing-your-first-application.html#howto.native-image.developing-your-first-application.buildpacks
    runImage = 'paketobuildpacks/ubuntu-noble-run'
    environment = [
            "BP_JVM_VERSION": "25", // GraalVM 25
            "BP_NATIVE_IMAGE_BUILD_ARGUMENTS": "$nativeImageBuildArguments",
    ]

    //    Use Oracle GraalVM to support PGO profiles
    buildpacks = [
            "docker://test-registry/dockerhub/paketobuildpacks/oracle:latest", "urn:cnb:builder:paketo-buildpacks/java-native-image"
    ]
}

Expected Behavior

Native image can be built with PGO profile applied.

Actual Behavior

Build fails with ClassCastException

Steps to Reproduce

Failing case:

1. create PGO profile with Spring Boot 3.5.9
2. try to build native image with Spring Boot 3.5.10 using the PGO profile
3. build fails

Successful case:

1. create PGO profile with Spring Boot 3.5.10
2. try to build native image with Spring Boot 3.5.10 using the PGO profile
3. build succeeds

I have attached a diff of the types referenced in the PGO profiles (removed application specific classes): diff-iprof-types.txt

Additional Context

I have not been able to access the generated error report (mentioned in the log output: /layers/paketo-buildpacks_native-image/native-image/svm_err_b_20260129T171259.740_pid408.md).

I would need advice how to extract that from such a Paketo build - didn't find anything in the Docker volumes.

Build Log Output and Error Messages

native-image-creator-output.log

[oubidar-Abderrahim]

Hi, Could you please try reproducing using a local installation of GraalVM 25.0.2 (without Paketo)? this also should help getting the svm_err file

[codesimplicity]

I tried that but failed to get far enough until I gave up. Simply too much manual setup and hassle if you don't have a local Linux.
Realised again, how much "magic" is involved in both Spring Boot native support and Paketo buildpacks.

The only realistic options I see are

• extracting more details from the PGO profiles (diffs of other jq queries)
• finding a way to access the error report from the Paketo layer

For applications that show this error, the workaround is to create a new profile first or build without a profile.

[wirthi]

The /layers/paketo-buildpacks_native-image/native-image/svm_err_b_20260129T171259.740_pid408.md file would be helpful for us. I find it surprising this is not accessible to you?

[codesimplicity]

The /layers/paketo-buildpacks_native-image/native-image/svm_err_b_20260129T171259.740_pid408.md file would be helpful for us. I find it surprising this is not accessible to you?

Any advice how I can access this would be helpful. I did find the directories for the Docker volumes created by the Paketo build but they were empty. Also didn't find any (working) option to specify some place outside Docker to keep such logs.

[wirthi]

Sorry, Paketo is outside my/our expertise, you need to clarify that with the Paketo Docs or Community.

Apart from that, I believe your error report is correct in principle - moving the PGO from one minor version to another should not end in a catastrophic build failure. We need to figure out what failed there (for that, the log file or a simple reproducer would be helpful). We are following up on that internally.

[codesimplicity]

Reached out to the Paketo team on Slack and they suggested to print that error report to stdout. Created paketo-buildpacks/native-image#390

Besides that, is there an option that GraalVM can write that error report to stdout instead of dumping it to a file?