Open SiriusStarr opened 12 years ago
How is doing the web ui in this case ? Does the shell hang or not ?
I'm sorry, I'm not quite sure I'm understanding what you're saying. Using the web interface in Firefox works fine, if that's what you're asking (it increases Firefox's memory use by ~60 MB), but everything stays responsive, and that's a reasonable amount of memory, not the >400 MB that the shell extension does. Or did you mean to try something else?
That's I was asking thanks.
Can you try the lastest code from github ? It may improve the performance of the extension.
Hmm, no luck. Upon first connecting to Transmission (e.g. I have the extension and I start Transmission), it will freeze Gnome (mouse moves, but all apps are unrepsonsive) for ~30-60 seconds. It's then fine if I just use the computer; no freezes or anything, so that's an improvement. But if I click on the indicator to actually open the extension (e.g. to view torrents), it once more freezes and becomes unreponsive for ~30-60 seconds.
I think this may just be an insurmountable issue with Gnome extensions that need to crunch a fair amount of memory, since the web interface works fine in Firefox. I know very little about the underlying architecture of Gnome with respect to extensions; could it just be a difference in speed between the javascript engines?
Well, I guess the time is spent in drawing with clutter each torrent in the menu and 1000 is just too much. If the menu is not open there is no repaint so this is because there is no problem, but when you open the menu, all torrents are repainted.
What about in setting a limit of drawn torrents in preferences? I'm not quite good in JS, but I think that's possible... Don't it?
Hi,
Firstly, I love the concept of this extension. Sadly, when I tried to use it, I found that it cannot deal with a large number of torrents. My transmission client has ~1200 torrents (seeding, not active). When this extension connects to transmission, it causes gnome-shell to jump to >500 MB of memory usage and peg my CPU at 100%, making the system unresponsive (until gnome-shell is killed). Anyways, I don't know if there is some potential workaround for this, but the capacity to handle such high-use scenarios would be much appreciated.
~Sirius