4/6/2024 0 Comments Track update error vuzeYou can use ShellExView (grab the 64-bit version) to disable them. C:\ProgramData\MEGAsync\ShellExtX64.dll. ![]() C:\Program Files\WindowGrid\WindowGrid64.dll.C:\Program Files\Listary\ListaryHook64.dll.C:\Program Files\Google\Drive\googledrivesync64.dll.C:\Program Files\AVAST Software\Avast\aswhook.dll.C:\Program Files\AVAST Software\Avast\aswAMSI.dll.C:\Program Files (x86)\RedFox\AnyDVD\ADvdDiscHlp64.dll.C:\Program Files (x86)\Microsoft Office\root\VFS\ProgramFilesCommonX64\Microsoft Shared\OFFICE16\MSOXEV.DLL.These are the non-Windows ones that the snapshot says are loaded into the process: If it does, re-enable a few at a time until it comes back, and you should be able to track down which one is causing it from there. I would try disabling all the shell extensions on your machine and then reboot, to see if that fixes the problem. Net at all, so we know they aren't ours) which are all doing various things, including network activity.Īvast Antivirus also looks like it's doing something, although it's hard to be sure if it's involved in the issue or not, since it's common for antivirus to get involved in any filesystem access. However, what I can tell from the single snapshot is that none of Opus's own threads are doing anything at all.īut something has created a large number of. That got lost when we split them out from another post. (Correction: The instructions used to say to make 5 or so. There's only one snapshot in the zip (the instructions say to make 5 or so) so I can't tell if some of what it shows was just executing when the snapshot was made by chance, or if it was always executing. You might also want to look at the config options or support forum for the NAS in question to see if it has any options to control how often it sends change notifications, or to make it not send notifications about the temp folders used by the torrent client. (They should only be on when debugging change notification issues, but it's easy to forget and leave them on by accident.) In the same place, make sure notify_debug and shellchange_debug are both False, as having them turned on can increase CPU usage when processing changes. They are more to help if the UI is not staying responsive. Preferences / Miscellaneous / Advanced : notify_max_time and notify_min_items can tweak how often Opus processes the queue, but probably won't help here. Preferences / File Operations / Options / Detect external file changes on network drives - Turn this off and there should be very little overhead from then on, but the downside is Opus will not notice changes made on network drives. ![]() (You'll still get the overhead when it is active, however.) When returning to the tab, it will be reloaded. Preferences / Folder Tabs / Options / Process file changes in background tabs - Turn this off and there will be less overhead from having the Y:\ tab in the background. If the latest version is installed, these settings may also help: NAT is fine, and Bigly is bound to the correct VPN interface.My guess is that when the torrents are downloading to that NAS, the NAS device (presumably not running Windows) is sending a flood of file change notifications, which Opus is using a lot of CPU and memory to keep up with.Īre you using the latest version of Opus? If you're on an old version, try updating first, as there are some improvements to how this kind of situation is handled. Or maybe simply Bigly is simply not taking into account IP address changes at all. ![]() It seem Bigly is failing to "say" something to all the trackers that it only does correctly on the 1st connection to the tracker (maybe because its expecting something which it never receives). But this is both annoying and inconvenient when you think your making progress on torrents only to find Bigly failed to reconnect for no good reason. The only way to fix this is to restart Bigly completely, the torrent will resume and connect to all the trackers without any problem at all in seconds. It seems BiglyBT isn't quering the trackers properly after a connection is lost and re-established.įor example if my VPN goes down (either on its own or if I swap server) then BiglyBT fails to ever (I've waited well over 2 hours) re-establish a connection to all trackers, it will just alternate between "Querying" and "Error: Offline - No data received from tracker".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |