- Biglybt cant end tassk how to#
- Biglybt cant end tassk utorrent#
- Biglybt cant end tassk android#
- Biglybt cant end tassk torrent#
Biglybt cant end tassk android#
When the biglybt GUI becomes unresponsive, often the Android app can still connect and control biglybt, but on this occasion it was locked up and I could only right-click on the biglybt taskbar entry and choose "close", then click on "force close" or whatever it is.
Biglybt cant end tassk utorrent#
When this happens, I see file access errors in utorrent as well, and vnc will not allow me to login until after I have logged into the tmux session - gives error "no password configured for vnc auth" until then.Īfter this happened today, the biglybt GUI became unclickable, as seems to happen fairly regularly even when there are no file access problems. I always have a tmux session running and Biglybt is running over vnc inside an encrypted /home, and for some reason that I haven't worked out yet, sometimes all programs running inside the vnc session lose write access to the /home folder until I reconnect to my tmux session. Allocation is 5x4, but minimum required size is 152x4.I'm using BiglyBT 3.0.0.0 on Ubuntu 18.04.6 LTS (Gnome). (BiglyBT:21831): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to underallocate SwtFixed's child GtkProgressBar 0x58cb0130. The next line has been another long running problem. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. (java:21808): Gtk-WARNING **: GTK+ module libgail.so cannot be loaded. The next line has been a long running problem which may or may not be connected to my slow exit problem. There is no way to make is stop re-occuring. My average upload speed in about 1 to 2 MB/s (Bytes).Īnother secondary problem, the Tor Helper Plugin pops up a window for 1/2 a second if all is running well or for 5 seconds if biglyBt is running slow. It used to be that if I could sneak up on biglyBt quickly after it started, and stop or pause all downloads, it would help the exit time. If I turn off my internet connection before closing biglyBt, it seems to make the slow exit problem more pronounced, more time. When I shut down all "detail" listing, in did not affect my slow exit problem.īy the way, there are other locations which have scrollbars, such as the bottom of most "spreadsheet" areas where the scrollbar interferes with the selection of a file or torrent. Noramlly, I liked to keep all torrents showing a "detail" entry on the left side. Now the scrollbar covers the x and it is not accesable. It used to be if you were extremely accurate and slow you might maybe be able to hit the x, around the scrollbar. This is because of the automatic scroll bar that appears when you are trying to point at the X. These x's used to be barely accessable and now are not.
Biglybt cant end tassk torrent#
Secondary problem: On the left sidebar where the torrent name is shown for the Details, there are many X's which should be used to close 1 detail at a time. This seemed to confuse biglyBt programming greatly. Of the same problem about slow exiting, nad when half of the details had closed, I pressed it again. This happened once when I closed all details, everything slowed to a crawl, because Secondary problem with "close all detail": Sometimes this button goes gray even when there are some details to close. "Close all detail" does not affect my slow exiting. Does "selection" mean 1 single plugin which is highlighted or all those with a check in the box? In the plugin dialog, there is a button for disable or uninstall selected. This is a secondary problem not connect to exiting slowly. By the way: The plugin function is difficult to understand and sometimes doesn't work. There may be something here to help track down the "process" which is slowing my biglyBt.
Biglybt cant end tassk how to#
Here is an article, most of which I don't understand, which may show how to track a memory or thread problem in a java vm. So I don't think the problem was re-introduce by a beta version. It was a few days later.ġ401B13 was running when I noticed the problem was back. The problem did not come back immediately after a new beta version. I listed this same problem a couple of months ago. In fact they are why I have been able to run biglyBt (and Vuze before). These setting are not the cause of the problem. I also set the other 2 ram java vm settings to 2gb
The reason most fuctions remain fast is probably because I have set the heap at 2gb of ram. Many of the biglyBt function are not as slow. The most obvious function is Exit, and "Transfers, Stop All", and some others which become tediously slow. There appears to be a part of biglyBt that is constantly running (endless loop?) and greatly slows some of biglyBt's functions down. I will touch on several issues, and focus on the main one. Exiting biglyBt takes 30 minutes or an hour or never, some process running in the background
0 kommentar(er)
