-
Notifications
You must be signed in to change notification settings - Fork 166
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.
Another way of getting a thread dump is to install VisualVM (https://visualvm.github.io/download.html), connect to the running BiglyBT process by double-clicking the entry under the "Local" heading in the sidebar, selecting the "Threads" tab on the right and then hitting the "Thread Dump" button on the far right of the view.
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/
Below is some older information regarding program crashes that may still be of relevance:
If you find that BiglyBT keeps crashing, it may be because something is wrong with BiglyBT , or something external is making it crash. Look at the suggestions below first to see if any of the below applications are causing BiglyBT to crash.
Known Causes
BiglyBT has logic to analyse crash dumps for evidence of them being caused by an internal browser error. If so then use of the internal browser within BiglyBT is automatically disabled.
To re-enable the internal browser when BiglyBT is running do the following:
Ensure your user 'Mode' is set to 'Advanced': Tools->Options->Mode Go to Tools->Options->Interface->Display, look for the 'Internal Browser' section towards the bottom and deselect the 'disable internal browser' checkbox and restart.
If you want to file a bug report then please include the hs_err_pid.log file.
Check hs_err_pid.log files, these may be in the BiglyBT program directory or in %user%\local\temp. These files are created by java system as java crash logs. It is possible that it will help you identifying the cause of the crash. The key part is looking for the java/DLL call stack thread leading to the crash. There should be something like:
JRE version: OpenJDK Runtime Environment (8.0_382-b05)
Java VM: OpenJDK 64-Bit Server VM (25.382-b05 mixed mode linux-amd64 compressed oops)
Problematic frame:
C Flash.ocx+0x54377
In the example's case the crash is caused by Adobe Flash player (used for displaying BiglyBT media browsing experienece through embedded IE components.) Identify the failing DLL. Consider removing the problematic application to see if that would help.
bigly help