Open nlisker opened 2 months ago
Can you try with 4.33 when it gets out (very soon) ? I would be wary of spending time investigating unless the problem is reproducible on 4.33.
A search for java.lang.NullPointerException: Cannot store to object array because "frame.stackItems" is null
in the defect data base brings up only this ticket. Notwithstanding that it would be good to know if 4.33 has the problem.
Yes, I intend to try on 4.33. It might take a while to update after its release because of 3rd party plugins that need to catch up.
I also searched for frame.stackItem
before submitting to see if it was handled, but didn't find anything.
Thanks @nlisker - I will also spend some time to see if I can unearth something here.
There has been a substantial overhaul and reimplementation of sealed types and switch exhaustiveness determination. It would be good if this could be tested against master HEAD at some point.
Using Eclipse Version: 2024-06 (4.32) Build id: I20240601-0610. Hopefully it was fixed for 4.33.
I'm getting compilation error on one of my larger classes:
The error appears on the first line of the class:
The log shows various stack traces that change as I manipulate the code:
and
Unfortunately, I couldn't find a minimal reproducer, although in my project I can reproduce it 100% of the time. The class looks something like this:
Editing out the
getEntity
method fixes the problem. Adding adefault
branch to the switch fixes it as well, although the switch is exhaustive.Without a reproducer it's difficult to find the issue, but I hope that the stack traces along with the description of what causes and alleviates the problem can be enough. If the stack trace guides towards something that should be in the class, I can find it in my project's class and copy it to the reproducer attempt to see if that changes things.