Closed csylvain closed 5 months ago
Not sure that exception is relevant - probably more likely to be related to the SWT library update I recently pushed to beta users.
I'll have a play and see if I can reproduce it.
In the meantime you might be able to attach to the looping JVM with jconsole
or dump threads via https://github.com/BiglySoftware/BiglyBT/wiki/Diagnostics
I've managed to reproduce it, just looking into how to fix
Try beta B12
i tried to dump threads using the Diagnostics URL - i submitted the URL to Beta 10 and waited .. and waited .. and gave up after an hour with the CPU spinning away at max.
any further suggestion(s) ? .. oh i refreshed, and see you suggest Beta 12. i am updating right now.
Hello, I just wanted to inform you, that I have the same issue. I am trying to install BiglyBt on a Docker with JDK17. Alll is updated. BiglyBT gets installed and then when I start it, I see the window and it hangs. Thanks and have a good day
I would like to add that I just tried to install v2.6 and I have the same issue. Strange...
i have been able to successfully exit BiglyBT a few times. seems fixed. thanks!
OS: Ubuntu 22.04.1 biglybt version number: presently 3.2.0.1_B10 (manually updated from B09 due to issue - copied new BiglyBT.jar over old) desktop: ubuntu standard (gnome?)
ever since "GUI error" message on start up has appeared, shutdown goes through all of the GUI termination but many java threads remain. one of the threads shows max CPU use via 'htop' and using the sigkill feature is the only way to actually terminate biglybt completely. in all other respects, biglybt appears to be fully functional.
this has been going on at least since the 3.2 beta series. it may be related to the "hangs network on shutdown" issue. automatic beta updating is affected negatively, as well. no version update occurs, although the new jar file is waiting in /tmp
Help -> About BiglyBT -> System info:
GUI error message in detail: