Ask Your Question
1

Why does tracker-store keep using more memory

asked 2018-10-19 09:15:42 -0600

dmradcliff gravatar image

I have been logging tracker-store memory usage in the background. The other day when I restarted my computer it was consuming nearly 3.5GB of memory. I can't attach a file so I am going to paste the contents here. As you can see the memory usage keeps increasing slowly over time. Eventually it just grows and grows until it consumes a large chunk of DDR. Any idea what is going on here and how I can stop this?

tail -f tracker-store.txt

Elapsed time CPU (%) Real (MB) Virtual (MB)

   0.000        0.000       30.035     1167.398
  60.060        0.200       30.387     1199.414
 120.120        0.100       30.387     1215.422
 180.182        0.100       30.387     1231.430
 240.242        0.100       30.387     1247.438
 300.302        0.100       30.664     1287.457
 360.364        0.100       30.664     1303.465
 420.424        0.000       30.816     1319.473
 480.486        0.100       30.816     1335.480
 540.548        0.000       30.816     1351.488
 600.610        0.100       30.816     1367.496
 660.672        0.000       30.816     1383.504
 720.734        0.100       30.816     1399.512
 780.796        0.000       30.902     1415.520
 840.856        0.100       30.902     1431.527
 900.918        0.100       30.902     1447.535
 960.978        0.100       30.902     1463.543
1021.040        0.000       30.902     1479.551
1081.100        0.100       30.980     1495.559
1141.161        0.000       30.980     1511.566
1201.222        0.100       30.980     1527.574
1261.282        0.100       30.980     1543.582
1321.337        0.100       30.980     1559.590
1381.396        0.100       31.059     1575.598
1441.456        0.000       31.059     1591.605
1501.515        0.100       31.059     1607.613
1561.576        0.000       31.059     1623.621
1621.635        0.100       31.059     1639.629
1681.695        0.000       31.148     1655.637
1741.755        0.100       31.148     1671.645
1801.814        0.100       31.148     1687.652
1861.874        0.100       31.148     1703.660
1921.934        0.000       31.148     1719.668
1981.991        0.100       31.148     1735.676
2042.050        0.100       31.230     1751.684
2102.110        0.100       31.230     1767.691
2162.170        0.100       31.230     1783.699
2222.231        0.000       31.230     1799.707
2282.291        0.100       31.230     1815.715
2342.351        0.100       31.320     1831.723
2402.411        0.100       31.320     1847.730
2462.471        0.000       31.320     1863.738
2522.531        0.100       31.320     1879.746
2582.591        0.000       31.320     1895.754
2642.651        0.100       31.320     1911.762
2702.711        0.100       31.402     1927.770
2762.772        0.100       31.402     1943.777
2822.831        0.000       31.402     1959.785
2882.891        0.100       31.402     1975.793
2942.951        0.100       31.402     1991.801
3003.011        0.000       31.402     2007.809
3063 ...
(more)
edit retag flag offensive close merge delete

Comments

hhlp gravatar imagehhlp ( 2018-10-20 07:00:31 -0600 )edit

@hhlp: This is not really helping.

genodeftest gravatar imagegenodeftest ( 2018-11-04 07:23:43 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2018-10-19 11:46:53 -0600

sdgathman gravatar image

The real memory is fairly constant in your table. Virtual memory includes things like memory mapped files. This behavior is completely normal if the database tracker-store maintains is memory mapped. Does the virtual memory continue where it left off when you reboot? Without knowing anything about the code in tracker-store, you can find its process id, and explore in /proc/nnnn - where nnnn is the process if of tracker-store.

http://man7.org/linux/man-pages/man5/...

You can see files mapped in /proc/[pid]/maps and a memory summary in /proc/[pid]/status.

Remember, "virtual memory" is a measure of address space used, NOT of actual ram used.

https://fedoramagazine.org/understand...

edit flag offensive delete link more

Comments

I understand virtual memory is not actual ram. But if you look at the original post, real memory was 3.5GB when I rebooted before taking this log. Letting this run over the weekend it went from the 31MB shown above to 87.7MB this morning and it continues to slowly increase. Virtual memory is not my problem. It is the continual chewing up of memory as seen by the increase of over 50MB over the weekend when my computer was idle the entire time and the 3.5GB of ram it was consuming before my last reboot. This is what I want to prevent.

dmradcliff gravatar imagedmradcliff ( 2018-10-22 12:57:02 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2018-10-19 09:15:42 -0600

Seen: 202 times

Last updated: Oct 19 '18