WaltS48 wrote:
On 4/14/17 11:25 AM, Dirk Munk wrote:
There is a maximum memory footprint for the 64 bit version of
SeaMonkey on Windows, what is causing that? With too many tabs open,
Seamonkey will crash. I suppose a 64 bit application shouldn't run
out of memory.
With about:memory , this shows up:
WARNING: the following values are negative or unreasonably large.
explicit/(19 tiny)
explicit/(19 tiny)/heap-unclassified
This indicates a defect in one or more memory reporters. The invalid
values are highlighted.
and:
└───-382.40 MB (-10.76%) -- (19 tiny) [?!]
├────30.30 MB (00.85%) ++ storage
├────24.38 MB (00.69%) ++ gfx
├────21.57 MB (00.61%) ++ xpconnect
├────20.48 MB (00.58%) ++ atom-tables
├─────4.94 MB (00.14%) ++ startup-cache
├─────4.14 MB (00.12%) ++ dom
├─────3.81 MB (00.11%) ++ workers
├─────3.32 MB (00.09%) ── spell-check
├─────2.97 MB (00.08%) ++ cycle-collector
├─────1.38 MB (00.04%) ── history-links-hashtable
├─────1.23 MB (00.03%) ── xpti-working-set
├─────1.12 MB (00.03%) ── cookie-service
├─────1.01 MB (00.03%) ── preferences
├─────0.62 MB (00.02%) ── telemetry
├─────0.56 MB (00.02%) ── icu
├─────0.30 MB (00.01%) ++ xpcom
├─────0.13 MB (00.00%) ++ media
├─────0.01 MB (00.00%) ── script-namespace-manager
└──-504.68 MB (-14.20%) ── heap-unclassified [?!]
I don't know the answer to your question.
Here is a Meta bug tracking memory problems.
<https://bugzilla.mozilla.org/show_bug.cgi?id=1311526>
Most likely these are 32 bit unsigned memory counters (counting the
memory in bytes), displayed as 32 bit signed values. Of course they
should be 64 bit counters.........
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
