-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ijar tool fails with segmentation fault #14645
Comments
There was another report of this in slack Do you have a repro, or can you share the jar it's crashing on in the bug? |
Apparently this is a problem for specific jar (pureconfig), I was able to find similar issues for the same Scala artifact:
Its weird that it has been working for us on bazel 4.x and earlier but started to break on 5.x. Closing this as a duplicate of #13943. |
It's not just for a specific jar. I can see a lot of other complaints about some random jars failing including us. I have some jars that I need urgently for my project and I can extract them on MacOS without any problem, but when used as a part of build I get that segmentation fault. |
Do you have a repro, or can you share one of the jars it's crashing on in the bug? |
We build some internal plugins that use compiled versions of IntelliJ-Community edition compiled by us. We have been doing this for years without any problem. Then suddenly when upgraded to Java 17 + latest EAP the files started throwing these errors. Using |
There were some other reports of ijar segfaults here:
For anyone seeing this, can you share one of the jars ijar is crashing on in the bug? |
@cushon I'm seeing this On
|
@youmna-rabie can you share one of the jars ijar is crashing on, perhaps by attaching it to a comment on this bug? |
@cushon I'm not able to share a JAR on here as it's not a supported file type, but here's a Google Drive link with the jar folder. |
I can reproduce with the version of ijar in Bazel 5.1.1, but not with the latest versions of ijar, this bug seems to have been fixed. Can you try using a newer version of Bazel? |
Do you know the lowest version of bazel that would have fixed this? This is a legacy code base that isn't easily upgrade-able unfortunately :/ |
Actually 6.3.0 also had the fix: dc1c7b3 |
Thanks, upgrading to 6.3.0 resolved it! |
Description of the problem / feature request:
I'm trying to migrate from bazel 4.2.2 to bazel 5.0.0 on Scala monorepo (with
rules_scala
) and started to see the following error:Looks like
ijar
fails with segfault during jar stamping step.It works perfectly fine with bazel 4 series (tested on 4.2.1 and 4.2.2).
What operating system are you running Bazel on?
Linux nzxt 5.4.0-96-generic #109-Ubuntu SMP Wed Jan 12 16:49:16 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
What's the output of
bazel info release
?release 5.0.0
The text was updated successfully, but these errors were encountered: