Decompiler misbehavior

[meiMingle]

Vineflower version

1.10.1

Describe the bug

In line 74 of the source code, The call to the limit method points to the java.nio.Buffer.In fact, this is no problem in the environment of JDK8 and below. But since JDK11, there is a method ByteBuffer limit(int newLimit); in the java.nio.ByteBuffer, which makes the situation different. If you recompile this decompiled code in an environment higher than jdk11, the limit method here will refer to java.nio.ByteBuffer#limit(int), which is inconsistent with the behavior in the source code.

Additional information

Steps to reproduce
1.Checkout https://github.com/Col-E/InstrumentationServer
2.Execute mvn compile
3.Compare the source code and class file of this method software.coley.instrument.io.ByteBufferSanitizer#ensureWriteable

Also reported here https://youtrack.jetbrains.com/issue/IDEA-353150/Decompiler-misbehavior

[zml2008]

Thanks for the report! In theory we should have handling for this issue, not sure why it's not behaving in this case?

[meiMingle]

In addition, the decompilation GUI tool I use is the dev4 branch of Recaf, which runs on my win10 computer, jdk22 (zulu22.30.13-ca)

[meiMingle]

JetBrains/intellij-community@3a9e1d2
This commit seems to solve this problem, I verified it using IDEA2024.2EAP3