fix: add special handling for Object in Types.newInstance() #2102
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
oracle/graal#11429 confirms a behavior problem when calling
Object.class.newInstance(). This is a temporary workaround while the GraalVM team looks into this.Since
Typesrelies onClass.newInstance(), we add a concrete case forjava.lang.Object.classto avoid the mysteriousSerializationSupport$StubForAbstractClassthat comes instead ofObjectin Graal 24 compiled images.More context and investigation in tracking doc.