[dash] High memory usage when performing a search

Bug #718591 reported by Mariano Chavero
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
unity-2d
Confirmed
Critical
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: unity

I have been testing Unity 2d under Maverick and I noticed that Unity Places leaks arround 260 mb of Ram of my 1gb whenever I perform a search on it's search box. It only happens if I keep the letters typed in the box (In current version the search box doesn't clear when Places launches the application) There is no problem whenever I clear the search box before Places exit out. Software Center says my current version is: 0.4-0ubuntu1~bzr405
Last time "Upgraded" was February 11.

Here's a screenshot attached from Unity Places leaking over 270 mb.

Hope this helps :)

Revision history for this message
Mariano Chavero (marianochavero) wrote :
Revision history for this message
Florian Boucault (fboucault) wrote :

Thanks for the bug report Mariano.

So, leaking memory is when the memory is never released during the lifetime of the process. I think what you are seeing here is rather a high usage of memory when search results are displayed.

Can you start a search and then execute the following in a terminal and capture the entire output?

ps aux

Changed in unity:
status: New → Invalid
Changed in unity (Ubuntu):
status: New → Invalid
Changed in unity-2d:
status: New → Incomplete
summary: - Unity 2d Places Memory leak when perform a search
+ [dash] Memory leak when performing a search
Revision history for this message
Mariano Chavero (marianochavero) wrote : Re: [dash] Memory leak when performing a search
Download full text (10.9 KiB)

I don't think this issue should be dismissed anyway. Should I open another bug report and replace "Memory Leak" with "High usage of memory during"?

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.1 23852 1776 ? Ss 11:34 0:01 /sbin/init
root 2 0.0 0.0 0 0 ? S 11:34 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? S 11:34 0:00 [ksoftirqd/0]
root 4 0.0 0.0 0 0 ? S 11:34 0:00 [migration/0]
root 5 0.0 0.0 0 0 ? S 11:34 0:00 [watchdog/0]
root 6 0.0 0.0 0 0 ? S 11:34 0:00 [events/0]
root 7 0.0 0.0 0 0 ? S 11:34 0:00 [cpuset]
root 8 0.0 0.0 0 0 ? S 11:34 0:00 [khelper]
root 9 0.0 0.0 0 0 ? S 11:34 0:00 [netns]
root 10 0.0 0.0 0 0 ? S 11:34 0:00 [async/mgr]
root 11 0.0 0.0 0 0 ? S 11:34 0:00 [pm]
root 12 0.0 0.0 0 0 ? S 11:34 0:00 [sync_supers]
root 13 0.0 0.0 0 0 ? S 11:34 0:00 [bdi-default]
root 14 0.0 0.0 0 0 ? S 11:34 0:00 [kintegrityd/0]
root 15 0.0 0.0 0 0 ? S 11:34 0:00 [kblockd/0]
root 16 0.0 0.0 0 0 ? S 11:34 0:00 [kacpid]
root 17 0.0 0.0 0 0 ? S 11:34 0:00 [kacpi_notify]
root 18 0.0 0.0 0 0 ? S 11:34 0:00 [kacpi_hotplug]
root 19 0.0 0.0 0 0 ? S 11:34 0:00 [ata_aux]
root 20 0.0 0.0 0 0 ? S 11:34 0:00 [ata_sff/0]
root 21 0.0 0.0 0 0 ? S 11:34 0:00 [khubd]
root 22 0.0 0.0 0 0 ? S 11:34 0:00 [kseriod]
root 23 0.0 0.0 0 0 ? S 11:34 0:00 [kmmcd]
root 25 0.0 0.0 0 0 ? S 11:34 0:00 [khungtaskd]
root 26 0.0 0.0 0 0 ? S 11:34 0:00 [kswapd0]
root 27 0.0 0.0 0 0 ? SN 11:34 0:00 [ksmd]
root 28 0.0 0.0 0 0 ? S 11:34 0:00 [aio/0]
root 29 0.0 0.0 0 0 ? S 11:34 0:00 [ecryptfs-kthr]
root 30 0.0 0.0 0 0 ? S 11:34 0:00 [crypto/0]
root 35 0.0 0.0 0 0 ? S 11:34 0:00 [pciehpd]
root 36 0.0 0.0 0 0 ? S 11:34 0:00 [scsi_eh_0]
root 37 0.0 0.0 0 0 ? S 11:34 0:00 [scsi_eh_1]
root 40 0.0 0.0 0 0 ? S 11:34 0:00 [kstriped]
root 41 0.0 0.0 0 0 ? S 11:34 0:00 [kmpathd/0]
root 42 0.0 0.0 0 0 ? S 11:34 0:00 [kmpath_handle]
root 43 0.0 0.0 0 0 ? S 11:34 0:00 [ksnapd]
root 44 0.0 0.0 0 0 ? S 11:34 0:00 [kondemand/0]
root 45 0.0 0.0 0 0 ? S 11:34 0:00 [kconservative]
root 232 0.0 0.0 0 0 ? S 11:34 0:00 [mp...

Revision history for this message
Florian Boucault (fboucault) wrote :

Don't worry the bug is not dismissed in any case.

Looking at the output of ps, unity-2d-places is using around 108MB of resident memory. That's a bit high and deserves further investigation.

summary: - [dash] Memory leak when performing a search
+ [dash] High memory usage when performing a search
Changed in unity-2d:
status: Incomplete → Confirmed
importance: Undecided → Medium
Changed in unity-2d:
importance: Medium → Critical
milestone: none → 3.8.4
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.