Bug 560124 - VerifyError: Inconsistent stackmap frames at branch target
Summary: VerifyError: Inconsistent stackmap frames at branch target
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.14   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-13 14:20 EST by Pascal Filion CLA
Modified: 2024-01-25 02:44 EST (History)
0 users

See Also:

Attachments
Stacktrace (13.43 KB, text/plain)
2020-02-13 14:20 EST, Pascal Filion CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Filion CLA 2020-02-13 14:20:01 EST 
Created attachment 281813 [details]
Stacktrace

Description:
- In Eclipse 4.13, everything works fine.
- Upgraded to 4.14 and got the problem at runtime.
- Reverted back to 4.13, did full rebuild, and the problem went away.

Java:
- JDK used is OpenJDK (openjdk-8u242-b08) or Oracle JDK (JDK 1.8.0_241)
- Everything is set to use JDK 1.8 (compiler, compliancy)
Comment 1 Eclipse Genie CLA 2022-02-03 10:53:17 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2024-01-25 02:44:28 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.