-
Notifications
You must be signed in to change notification settings - Fork 161
Diagnostics
If the user-interface stops responding it is sometimes possible to grab some diagnostics to help debug the issue. Open a browser and navigate to
http://127.0.0.1:45100/setinfo?name=AZMSG&value=AZMSG;0;config;log-diags;;
(make sure you include the double ;; at the end of that)
If this 'page' loads (if it doesn't load you will get an error such as 'connection refused', if it does load then you will see some kind of result such as a black page) then check the debug_1.log / debug_2.log as one of these should contain some stack traces that might pinpoint the issue - these are in the 'logs' directory of the BiglyBT config folder (%appdata%\BiglyBT on Windows). The thread state is also dumped into a log file named 'ThreadDump.log'.
There is also a "slow UI" log in the logs directory. This captures events that have caused the UI to be slow to react and can reveal the underlying cause.
Refer to Performance-Tweaks for information on diagosing CPU/Memory issues.
BiglyBT uses your internet extensively to operate, not just for downloading files but also for the decentralised features such as decentralise tracking, ratings/omments and swarm discoveries.
If you have a limited internet connection or device that isn't capable of supporting a high level of network activity then you may notice degredation to other applications that also share that resource. For example your internet browser might respond more slowly.
To reduce BiglyBT's network usage there are several things you can do - this will cause BiglyBT to behave in a non-optimal way but it is a trade off you can decide to make.
- Limit BiglyBT's maximum upload/download speeds - you should ensure there is enough bandwidth available for other applications. In particular limit upload speeds to at most 80% of your internet connection's maximum speed (Options->Transfer)
- Limit the number of peer connections (Options->Transfer)
- Make sure you haven't installed the 'I2P Helper' plugin - if you have then uninstall it (Tools->Plugins->Uninstallation Wizard)
- Disable the 'Distributed Database' (DHT) under Options->Plugins->Distributed DB
If BiglyBT fails to start (you attempt to start it and nothing happens or it appears to start and then vanishes) then you need to start it with a console visible to grab some diagnostics. On Windows this is done by finding "BiglyBT-console.exe" (usually in C:\Program Files\BiglyBT) and launching this instead of "BiglyBT.exe". This will generate diagnostics in a command window. If this window itself disappears then start a command prompt (via "cmd.exe"), navigate to the BiglyBT folder ("cd C:\Program Files\BiglyBT" and "enter") and run it manually (type "BiglyBT-console.exe" and then "enter")
Then inspect the logging for anything suspicious.
Look for something like
Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/swt/graphics/Device has been compiled by a more recent version of the Java Runtime
If you see this check out https://github.com/BiglySoftware/BiglyBT/issues/3508
Issues can be reported by going to https://github.com/BiglySoftware/BiglyBT/issues - please search for existing information about your problem before raising a new issue.
To help diagnose issues you can attach a 'debug.zip' file to your report, go to the Help menu in BiglyBT and select the menu option to generate debug information.
For general discussion, rather than specific issues, please use reddit - https://www.reddit.com/r/BiglyBT/
bigly help