Closed Bug 1616551 Opened 4 years ago Closed 3 years ago

Severe memory usage

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Version:
SeaMonkey 2.53 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: americasdeath.isblacks, Unassigned)

References

Details

Attachments

(11 files)

Seamonkey2.53.2_memoryLeak.png
176.69 KB, image/png
Details
Seamonkey2.53.3_memoryLeak5.8GB.png
204.88 KB, image/png
Details
Seamonkey2.53.3_memoryLeak40GB.png
260.05 KB, image/png
Details
memory-report.json_justBrowserStartOffline.gz
113.88 KB, application/gzip
Details
memory-report.json_startedMail.gz
119.32 KB, application/gzip
Details
memory-report.json_IMAPsynch.gz
121.45 KB, application/gzip
Details
memory-report.json_2days.gz
166.80 KB, application/gzip
Details
memory-report.json_4days.gz
231.87 KB, application/gzip
Details
Seamonkey2.53.3_memoryLeak7GB.png
254.72 KB, image/png
Details
memory-report.json_8GB.gz
690.24 KB, application/gzip
Details
Memory1.jpg
155.63 KB, image/jpeg
Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.1 Lightning/5.8.1

Steps to reproduce:

Just had to browse the internet, on any given day, any given time.

I could have only one site open, or 4 tabs or more and it could end up all the same - getting so slow and waiting for clicks on links to happen or pages to scroll, etc.

Actual results:

It seems eventually Seamonkey starts to eat RAM. I'm not sure when or how, as it seems to happen randomly and no specific websites.

One minute things are going just fine, the next thing I know I'm waiting for the cursor to change when hovering on a link or waiting for the page to scroll, etc. The delays in things to happen usually are a couple seconds but no more than three seconds so far, but the delay in every thing I want to do, not just surfing, but doing anything on my computer, has that short delay anytime I want to do anything.

When I open ksysguard to see what might be the problem app, it's Seamonkey using 2+ GB of RAM (of my 12GB).

If I close Seamonkey and open/use Firefox (for instance) and go to the same sites I was just on, with the same number of tabs of the same sites, nothing is going wrong and ksysguard shows it only using around 190MB of RAM, so this was my non-scientific, simpleton test, heh.

Expected results:

Nothing other than just continue to not have the sudden delays for anything to happen on my computer when it suddenly starts to eat RAM.

This is Seamonkey 2.53.1b1

I'm also experiencing severe slowdowns with SeaMonkey 2.53.1 on x86_64 (openSUSE Tumbleweed). After running the browser for a while, clicks and scrolling take several seconds to register, and I can type much faster than text appears in form input and textarea fields. I didn't have any such problems with SeaMonkey 2.49. According to htop and ksysguard, SeaMonkey is using about 2.5 GB of RAM out of my 16 GB total, whereas memory usage with SeaMonkey 2.49 was around 800 MB.

Possibly related/duplicate: Bug 1634973

(In reply to Tristan Miller from comment #2)

Possibly related/duplicate: Bug 1634973

Sorry, copy-and-paste error—I meant to write Bug 1633339.

Incidentally, the problem described in the present bug report is still present in SeaMonkey 2.53.2. In my case, htop has been reporting memory usage of over 20 GB.

A very reliable way to trigger this bug is to use Google Maps street view to navigate down a street. Each time you advance down a path, another 100 MB or so of memory gets allocated. On my system, with 16 GB of memory, I can't use street view like this for more than a few minutes without making SeaMonkey completely unusable. Forcing GC/CC/minimization in about:memory doesn't help for long.

A very reliable way to trigger this bug is to use Google Maps street view to navigate down a street.

Unfortunately not here under Windows 8.1 x64. Adds 50 to 100 MB but also frees them. Ended the tour with 1500 MB and a manual GC bought it down to the initial 300 MB. But This is 2.53.4b1 pre. uBlock origin and NoScript in place. All google sites are not whitelisted. I only do this on a case by case base.

Is your problem with the distributed build?

28 GB is really too much, with Seamonkey 2.49.5 never saw such memory hungry situations

(In reply to Valerio Messina from comment #8)

28 GB is really too much, with Seamonkey 2.49.5 never saw such memory hungry situations

Does it do the same if you don't start the mail side? Is it IMAP or POP3 mail you use SeaMonkey for?

Flags: needinfo?(efa)

I use IMAP with three accounts, with many subfolders each.
Just immediately after Seamonkey mail and browser startup, it does the mail accounts sync, and the memory used is 908 MiB and 3.8 GiB virtual memory (just checked).
The memory used become much more in next time leaving the mail and browser on.
I never use it without Mail client as this is my mail client

Flags: needinfo?(efa)

repeated a second once and the result is little different:
Mail only after IMAP synch, use 2.5 GiB virtual and 275 MiB memory
Then set Work Offline, start Browser and memory become: 2.7 GiB virtual and 494 MiB Browser

just tryed running Seamonkey browser without start the mail client.
Just immediately after browser start, it use 2.4 GiB of memory and 377 MiB of virtual memory.
Then selected "Work offline" and started the mail client. The memory usage increased to 2.4 GiB and 442 MiB.
Going online and sync my IMAP accounts increased the memory usage to 2.7 GiB and 498 MiB virtual memory

sorry, the greather value of the two is always the virtual memory

attached two shots with v.2.53.3 where the memory leak is still there

(In reply to Valerio Messina from comment #16)

attached two shots with v.2.53.3 where the memory leak is still there

What would be useful is to look at the information in about:memory
Do a measure before starting the email side and then another once the email has finished its sync.
If you want there are buttons that let you "Measure & Save" and "Load & Diff" to help compare

already made the test looking at system resource monitor without starting the mail client 1 month ago, the results is described 7 post ago.
Anyway I'll redo the test looking at "about:memory"

I just attached three memory:usage measurements:.
I set Seamonkey in offline mode and quit, then:

  1. started the browser only. 2 windows, many tabs
    about:memory say: 2,881.39 MB ── vsize
    system monitor say: 2.8 GB + 495 MB
  2. started the mail client too (still in offline mode)
    about:memory say: 2,930.72 MB ── vsize
    system monitor say: 2.9 GB + 557 MB
  3. go online and synch my two IMAP accounts
    about:memory say: 2,975.22 MB ── vsize
    system monitor say: 2.9 GB + 570 MB
    I can confirm System monitor and about:memory report the same values

Leaving the browser run for some time and going to many websites, the memory increase to a level the system become unresponsive.
I had to close Seamonkey and restart it to regain free memory and no PC lag

Note that virtual memory is not real memory, it's not to be used as a measure of how much physical memory the browser uses.

I just attached the memory:usage measurements, after two days of browser running.

It show some strange negative values. It say:

WARNING: the following values are negative or unreasonably large.
explicit/(22 tiny)
explicit/(22 tiny)/heap-unclassified
This indicates a defect in one or more memory reporters. The invalid values are highlighted.

There is imho nothing really worrying in the memory dumps. Heap allocation did go up a lot if you just comare it with one of the earlier ones but I would expect this after 2 days. Three ghost windows which is generall not good but they don't seem to add many resources.

The negative values might be the real problem but hard to say. There are still bugs open for this in current Gecko.

If you leave SeaMonkey open for days the garbage collector might have some issues especially if you use it for browsing without and ad or script blocker. 2 of the ghost windows are google ones and I have seen delays with some google content.

OK, I used to keep 2.49.x versions for about two months without this issue

just attached the report after 4 days, the memory of PC is completely full (is a 4 GB RAM system) and it start to swap and become unresponsive.
The GC clean free about 800 MB and the system back to usability, but after a while the memory become full again.

just attached the report after 4 days, the memory of PC is completely full (is a 4 GB RAM system)

Mail usage grew to 1.3GB. Not sure how big you mail database is but this is probably the cause for the slowdown. If hardsisk and not SSD the swapping will kill performance. Also ghost windows more that doubled. Most are because of google ads and friends. This together with a very limited amount of physical ram (4 GB is not much these days and I consider 8GB a minimum with an x64 OS) probably contribute to it. Use uBlock and NoScript and at least the ghost windows should vanish.

I migrated to a new PC with 16 GB of RAM, leave Seamonkey running for 7 days, it consume 7-8 GB of real RAM.
I'm pretty sure if I leave it running for some other days it will end consuming also the 16 GB of RAM

2.53.4 do the same. After some days of Seamonkey running, the used memory is about 6 GB, and the PC start to be unresponsive. GC, CC and Minimize Memory Usage reduce a little the memory used, but stop freezing. After some hours, restart freezing.

I've experienced the same problem. In SeaMonkey 2.53.4 it got even worse.
I recognized that memory starts increasing on websites with excessive use of JavaScript like facebook or youtube. With multiple open Seamonkey windows, memory of 3 to 6 GB is used after a while and it becomes extremely slow. Opening a new window or zooming into a picture on Facebook can result in Seamonkey not responding anymore.

Attached image Memory1.jpg —

Today I did GC/CC/Minimize memory usage in about:memory. After I measured memory again, I found this warning in the report.

(In reply to Frank-Rainer Grahl (:frg) from comment #30)

Use uBlock and NoScript and at least the ghost windows should vanish.
using Search in Seamonkey Add-On I cannot find Extentions called NoScript or uBlock

Hello,

Let me say that you got the same type of errors on both Firefox and Seamonkey.

Just try to open 6 or 7 tabs on the same windows from websites streaming webcams or videos and you will have the same result.

I try something that could help and seems to be a long time issue with the gecko engine : cache managing.

When this excessive memory usage happens , empty the cache and reload the web browsers windows or tabs.

Sometimes it helps (sometimes lol )

(In reply to Frank-Rainer Grahl (:frg) from comment #5)

A very reliable way to trigger this bug is to use Google Maps street view to navigate down a street.

Unfortunately not here under Windows 8.1 x64. Adds 50 to 100 MB but also frees them. Ended the tour with 1500 MB and a manual GC bought it down to the initial 300 MB. But This is 2.53.4b1 pre. uBlock origin and NoScript in place. All google sites are not whitelisted. I only do this on a case by case base.

Is your problem with the distributed build?

Sorry, I'd overlooked this question. Yes, the problem occurs with the RPMs I package for openSUSE. I am also running uBlock origin (but not NoScript).

The problem seems to have improved somewhat in the last few months (currently I'm running 2.53.5.1) but SeaMonkey still becomes unusable on my older 4 GB machines after an hour or so of normal web browsing. Going to about:memory and doing the garbage/cycle collection and memory minimization on these systems results in no improvement (or at least, no improvement that lasts more than a few minutes).

I can try running the official build for a while if you think that will make any difference.

SeaMonkey 2.53.6b1 was released today. We switched to newer compilers for Linux x64 (gcc 8) and macOS (clang 8). Also Windows x86 is now done with clang 11 because of crashes with msvc. rust 1.47 is now used. I am not sure if this affects the perceived slowdowns but please give it a try and maybe use if for a few days instead of the distribution version.
Profile is still compatible with 2.53.5 but if you go back Lightning and language packes need to be reinstalled manually.
A bit unrelated I tested the Linux verision yesterday on OpenSUSE Leap 15.3. Could anyone on OpenSUSE 15.x please check if Profile Folder -> Open Folder works. Didn't for me but 15.3 is still prerelease code and worked in my Linux vms with different OS distributions.

(In reply to Frank-Rainer Grahl (:frg) from comment #40)

SeaMonkey 2.53.6b1 was released today. We switched to newer compilers for Linux x64 (gcc 8) and macOS (clang 8). Also Windows x86 is now done with clang 11 because of crashes with msvc. rust 1.47 is now used. I am not sure if this affects the perceived slowdowns but please give it a try and maybe use if for a few days instead of the distribution version.

I'll do so and report back.

A bit unrelated I tested the Linux verision yesterday on OpenSUSE Leap 15.3. Could anyone on OpenSUSE 15.x please check if Profile Folder -> Open Folder works. Didn't for me but 15.3 is still prerelease code and worked in my Linux vms with different OS distributions.

I can test if you tell me where to find this command.

I can test if you tell me where to find this command.
Just fixed it. Needed desktop-file-utils. It is in about:support/Troubleshooting Information but also about:profiles Open Folder.

As another side note 4GB and x64 is a minimum these days. Some websites uses one or two gigabytes of memory easy when playing back media. And no ad and/or scriptblocker constantly reload junk from the net too. That does not mean there is no room for improvement in SeaMonkey.

the comparison with Seamonkey 2.49.5 is important, and this can be considered a regression. 2.49 can be used for months with no problem on a system with 4 GB of RAM. Users can't swich back to 2.49 easily as the user profile was updated

within the latest nightly version, SM had always a softcrash at the end of excessive and continuous growing memory-consumtion.
Test was: www.mopo.de go there and do nothing for at least one hour.
Tried this again with the final 2.5.6 - and voila, it works now. Thanks.

m.

for me "version 2.53.6 beta 1" solved this, till now I never saw total mem allocation higher than 2.6 GB

while 2.53.6b1.en-US.linux-x86_64 worked good in low memory allocation and no PC freezing, final 2.53.6.en-US.linux-x86_64 use same low memory BUT after some days of use, PC start to be unresponsive.
GC, CC and Minimize Memory Usage reduce a little the memory used, but stop freezing.
After some days, restart freezing.

about:memory, Measure still show some negative (signed/unsigned bug) telemetry:

Main Process

WARNING: the following values are negative or unreasonably large.

explicit/(23 tiny)
explicit/(23 tiny)/heap-unclassified

This indicates a defect in one or more memory reporters. The invalid values are highlighted.
-1,475.00 MB (-36.55%) -- (23 tiny) [?!]
...
-1,571.81 MB (-38.94%) ── heap-unclassified [?!]

I saw the negative memory stats myself a couple of days ago and freaked out. I check the memory quite often since SM becomes so bloated and slow.

I check the memory quite often since SM becomes so bloated and slow.

Well enough is enough. This is a bug tracker and not a gossip page. We are fixing issues as fast as we can. We are now at comment 49 and about a third to 50% are just whining. Use another browser if you don't like it or help out with development. SeaMonkey 1.1 runs with probably in about 100 MB. It is either keeping up with new web standards or standing still. And yes it is not pefect and has problems with some pages.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
Restrict Comments: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: