Opened 5 years ago

Closed 4 years ago

Last modified 4 years ago

#2319 closed bug (WorksForMe)

Leak in webui

Reported by: Naddiseo Owned by: damoxc
Priority: major Milestone: not applicable
Component: Web UI Version: 1.3.6
Keywords: Cc:

Description

If I leave the webui running in a tab on chromium for a few hours, it uses all my RAM, and brings my system to a halt. I'm not sure how to proceed debugging it.

Change History (7)

comment:1 Changed 5 years ago by Cas

Are talking about chromium or deluge-web?

comment:2 Changed 5 years ago by Naddiseo

Given that I leave my browser open all the time with about 10 other tabs open, and chromium's task manager reports that none of the other tabs use more than ~150mb, I'm inclined to say it's deluge-web and/or its interaction with chromium.

comment:3 Changed 5 years ago by Cas

Please can you provide exact details of which process is causing the issue using system manager or top/htop.

Also please provide more details of OS, deluge setup etc...

comment:4 Changed 5 years ago by Naddiseo

There are two systems involved, my laptop and a server.

My laptop: $ apt-cache policy chromium-browser chromium-browser:

Installed: 25.0.1364.160-0ubuntu3

$ free -m

total used free shared buffers cached

Mem: 7777 6511 1266 0 249 1846 -/+ buffers/cache: 4415 3362 Swap: 12286 4761 7525

And the server: $ apt-cache policy deluge-webui deluge-webui:

Installed: 1.3.6-0ubuntu2

I'll run the tab again tonight, and post the top in the morning.

comment:5 Changed 5 years ago by Naddiseo

After three hours of running, I have the following:

A copy of running top, chromium's task manager reports that the deluge webui tab is pid 22155, which is the 4th down.

top - 23:02:14 up 8 days, 10:38,  3 users,  load average: 2.16, 2.15, 2.14
Tasks: 225 total,   3 running, 219 sleeping,   0 stopped,   3 zombie
%Cpu(s): 26.0 us,  0.8 sy,  0.0 ni, 72.8 id,  0.1 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem:   7964376 total,  7732940 used,   231436 free,   200172 buffers
KiB Swap: 12581884 total,  4730432 used,  7851452 free,  1101316 cached
pid to signal/kill 
  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND           
  895 richard   20   0 4872m 3.1g  13m R  88.8 40.4 690:26.97 chromium-browse   
 9483 richard   20   0  971m 171m  32m R   6.3  2.2 199:30.62 chromium-browse   
 3483 richard   20   0 2039m 235m  18m S   4.0  3.0 351:23.05 gnome-shell       
22155 richard   20   0 1965m 1.1g  21m S   4.0 14.8  14:09.16 chromium-browse  
 1578 root      20   0  475m  69m  52m S   2.7  0.9 246:48.69 Xorg              
21677 richard   20   0 5265m 286m 9560 S   2.3  3.7 145:22.04 java              
 9714 richard   20   0 1069m 163m  16m S   1.0  2.1  15:48.98 chromium-browse   
 4099 richard   20   0  663m  22m 8008 S   0.7  0.3   5:55.23 gnome-terminal    
 9728 richard   20   0  925m  54m  15m S   0.3  0.7   1:40.87 chromium-browse   
29965 richard   20   0 20640 1600 1104 R   0.3  0.0   0:00.67 top               
29975 richard   20   0  918m  68m  23m S   0.3  0.9   0:05.55 chromium-browse 

The top one, PID 895, is the combination of all my chomium tabs which is why it's reporting a lot of cpu and mem.

Chromium's task manager also says that the javascript memory is ~45K (22k live). Not sure if that's kilobyte, or number of javascript objects.

comment:6 Changed 4 years ago by Cas

  • Milestone changed from Future to not applicable
  • Resolution set to WorksForMe
  • Status changed from new to closed

comment:7 Changed 4 years ago by bro

The number of torrents loaded is probably relevant here.

Note: See TracTickets for help on using tickets.