Skip to content

Diagnostics

parg edited this page Mar 24, 2024 · 8 revisions

BiglyBT hangs or is slow to respond/react

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.

High CPU usage

Refer to Performance-Tweaks for information on diagosing CPU issues.

Reporting Problems

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.

Internet issues when BiglyBT is running

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