Created attachment 1235536 [details]
Java crash log
Description of problem:
If on gradle version > 3.1 I setup any jvm arguments like:
org.gradle.jvmargs=-Xms256m -Xmx1024m -Dfile.encoding=utf-8
to honor it gradle fork separate machine.
On top of stack always:
Stack: [0x00007f5e5d63c000,0x00007f5e5d73d000], sp=0x00007f5e5d737190, free space=1004k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libjansi.so+0xf38] Java_org_fusesource_jansi_internal_CLibrary_init+0x108
According to call Java_org_fusesource_jansi_internal_CLibrary_init I do assumption it is because of ANSI colors output handling.
Version-Release number of selected component (if applicable):
$ rpm -qa java\*openjdk\*
But unfortunately I have no small demonstration of code…
The crash seems to be caused by libjansi.so, so it may be in that library native code, I'm moving the bug for now.
Did you some research on that problem?
Guys this prevent from updating gradle in projects. Could you please look on it?
I little dig into problem and it seams more like gradle issue instead of java itself: https://github.com/gradle/gradle/issues/778#issuecomment-283348494
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Does the crash happen with JANSI shipped by Fedora? Anyway, without reproducer I won't be able to do much.
I can see that JANSI library is not the one shipped by us, it is from /home/pasha/.gradle/native/jansi/1.14/linux64/libjansi.so
So it's not a problem with jansi packages.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.