Bug 244879 - Does www/firefox on KDE have a memory leak?
Summary: Does www/firefox on KDE have a memory leak?
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-gecko (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-18 05:14 UTC by jdrch
Modified: 2020-03-18 06:00 UTC (History)
1 user (show)

See Also:
jbeich: maintainer-feedback+

Attachments
KSysMonitor Screenshot (68.20 KB, image/png)
2020-03-18 05:14 UTC, jdrch 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jdrch 2020-03-18 05:14:56 UTC 
Created attachment 212485 [details]
KSysMonitor Screenshot

Firefox appears to be using an inordinate amount of RAM on 12.1-RELEASE-p2 with the latest pkg repo enabled. Attached screenshot is RAM usage with 6 tabs open: Reddit, GitHub, Resilio Sync Forums, Stack Exchange, Bugzilla, and Glances documentation. Is this expected?
Comment 1 Jan Beich freebsd_committer freebsd_triage 2020-03-18 05:27:57 UTC 
Comment on attachment 212485 [details]
KSysMonitor Screenshot

Memory usage looks fine to me i.e., parent/main process tends to use more than child processes (web content, extensions, etc). mozjemalloc (a heavily modified version of jemalloc) hasn't been ported to FreeBSD or any other BSD, so each "firefox" process uses more memory than on Linux.

If you want to reduce memory usage at the cost of performance try starting like

  $ MALLOC_CONF="narenas:1,tcache:false" firefox
Comment 2 jdrch 2020-03-18 05:33:23 UTC 
(In reply to Jan Beich from comment #1)
Ah that would make sense, then. Thanks! I guess this can be closed.
Comment 3 Jan Beich freebsd_committer freebsd_triage 2020-03-18 06:00:25 UTC 
All the missing features are (supposed to be) documented in pkg-message. I've tried to port mozjemalloc long ago but gave up.

https://bugzilla.mozilla.org/show_bug.cgi?id=1153683