openJDK bug filing?

[Brian Bouterse]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Thanks Mario and Dalibor for the replies. Is there someone out there
who is willing to file this poorly written bug:

PyCharm is unusable with openJDK 1.8.0 on fedora 22. It works great
with the Oracle JDK and it worked well enough with openJDK 1.7.x.

I'm using the latest patched fedora 22, openJDK 1.8.0, and PyCharm
4.5.3 (the latest as of this writing). Before upgrading to fedora 22 I
was using fedora 20 which came with openJDK 1.7.x, and things worked
well enough. Not nearly as well the Oracle JDK, but well enough. After
upgrading to openJDK 1.8.0 pyCharm (same version as before) is
completely unusable. The program regularly sits at between 150 - 500%
of my cpu and freezes for minutes at a time. It's all CPU bound
although the application appears to be doing nothing useful.

- From the PyCharm logs, PyCharm support indicates that the threads of
PyCharm are significantly slower for "read actions from the file
system and loading classes from the classpath". PyCharm starts 50+
threads which isn't great, but the same PyCharm (and its threads)
worked on the openJDK 1.7.x. What changed in between 1.7.x and 1.8.0
that could have made this unusable? What can be done to fix this?

Anyone who installs f22, installs the latest pycharm will find it
totally unusable. This is a very easy bug to reproduce. If no one is
willing to file this for me then I'll eventually file it at bugs.sun.com
.

Thanks!
Brian


On 08/26/2015 12:13 PM, Mario Torre wrote:
> On Wed, 2015-08-26 at 11:15 -0400, Brian Bouterse wrote:
>> I have a bug that I would like to file. I think openJDK bugs are 
>> tracker here [0], but I do not know how to login to that system
>> to make a bug. I see here [1] that self-service account creation
>> is not available. How can I file a bug so I can then discuss it
>> on this dev lis t?
>> 
>> [0]: https://bugs.openjdk.java.net/browse/JDK [1]:
>> https://wiki.openjdk.java.net/display/general/JBS+Overview
> 
> Unfortunately the situation is a bit chaotic if you lack Jira
> super powers.
> 
> For *JDK 8 and 9, what Dalibor suggested is an option, although is
> not an optimal solution at all... like none of the alternatives 
> unfortunately.
> 
> If the bug is specific to 7 or 6, you would need to file in the
> IcedTea bug system (again, in case you don't have Jira powers),
> which is even more confusing for end users because those external
> trackers are not really related.
> 
> You could have better luck filing the issue with the relative
> downstream Java and let the maintainers propagate the bug upstream,
> that means, again, bugs.sun.com if you are using an Oracle JDK, or
> Red Hat bugzilla if your using a Red Hat package, or even IcedTea
> directly, etc...
> 
> Another alternative which still require some substantial work from 
> OpenJDK members is to try to make a case and get somebody file the
> bug for you, in this case the mailing list is a better place.
> 
> If it's a security bug, discussing on the mailing list is not the
> best approach, you should contact Oracle and let them guide you.
> 
> But if you have a patch you may try to submit to the relevant
> mailing list for discussing the fix directly, it doesn't make
> things magically easier, but it helps a little bit.
> 
> Cheers, Mario
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJV3f8OAAoJEK48cdELyEfylqUH+gIMEri1GpAWv7Q3QT57crnD
CQjLAWA9X+rMUVldNtn5Q4vGi9S0pjK0bAvdFOyA3RVhgR9HSI7dFLp7bbk2WaLJ
IIXYzvyeQ5S4zyFKTbHfP3GdVQJ8/Xq/nEjjQpGuI9TZFkf68uc2Eqb93m8aLjHB
ZaEdH5Nx1FrGj3lnqbCVReQy79g6FiG/nwLcOZmh7x+VwaMwaw9CSwtGmXIv6gs1
uiAvRMxzJhYxNTzhWBZ7e9TBDjmTLoOHbHPMbu8qQw+tUroPJWsW3lBJMEM2jfzZ
36vXmlN3gJtkkgYFR48C3KyGsSyMz4UtLq5tmNMAsgdCKnlG60WDfGiaRbzd/po=
=BEtH
-----END PGP SIGNATURE-----