Closed Snake883 closed 1 year ago
Can you describe what BiglyBT was doing at the time this was taken?
2 more questions: Can you tell me how to re-create the issue? Also, does it happen with v3.2.0.0?
docker pull fullaxx/biglybt:3.2.0.0
If this is related to a configuration item, I'd be happy to change the defaults. If BiglyBT was checking files, then this is normal behavior. If it's a bug, then it should be relayed to the developers of BiglyBT.
If your CPUs are pegged, then the user experience will suffer, there is nothing I can do about that. You might consider using another torrent client if this behavior becomes routine. I switched to QBitTorrent a long time ago. https://github.com/Fullaxx/qbittorrent I prefer it to BiglyBT.
The Java VM is constantly using a lot of CPU. The container is also painfully slow.
Java 11.0.18 (64 bit) Ubuntu /usr/lib/jvm/java-11-openjdk-amd64
SWT v4942r22, gtk/3.24.33, zoom=100, dpi=96 Linux v5.19.17-Unraid, amd64 (64 bit) B3.3.0.0/4 az3