1491057 - soft-crash

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[mhonline]

Attachment: 180911_memory.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4
Build ID: 20180713174829

Steps to reproduce:

for example noteboockcheck.com


Actual results:

soft-crash of SM 2.49.4 - SM and system W10/H64 stalls until SM is terminated 
SM establishes to many connections to one server while not freeing memory
(Firefox KLAR or IRON don't do so)

Comment 1

[Frank-Rainer Grahl (:frg)]

The site www.notbookcheck.com loads fine here but I am using NoScript and ublock 1.16. Do you have a problem with a specific link or video?

If you don't use an ad- or scriptblocker it is probably some external javascript running amok or the site itself might use bad browser sniffing. Norton antivirus software is also good for problems because it injects itself into the browser process. Without a crash report probably nothing we can do. Does Firefox 52.9 work?

Comment 2

[mhonline]

That site is ment as a drastical example only, sourceforge and many more sites behave the same way, esp. those linking to many third-party-servers (btw. this is the unexpected outcome of the new EU-DSGVO, since the request to "accept cookies" seems to be treated an permission/invitation to establsh more cookies/connection than before)
Anyway, longterm usage of SM will make the machine run out of memory.
And no, SM is used in here as the browser WITH script-usage and WITHOUT ad-blocker, since some sites otherwise do not work, like spiegel.de etc...

To my point of view, SM did not changed that much whereas the many web-sites changed their behavior, and SM-development did not react on that: Not freeing memory and accepting too many connection to one server (note, that more than 100 connetions in one time or 10andplus to one server is breaking my router too!)
Solutions should be easy, for example with a switch/setting within option-menu (not via about:config) or rejecting 0-pixel-images and so on ...
my2cents
m.

Comment 3

[mhonline]

Attachment: example with virgin SM-start to one page only(ADOBE past flash-update)

Comment 4

[Frank-Rainer Grahl (:frg)]

There is nothing we can do here. Website rendering is done by Gecko. The Spidermonkey component does the javascript processing. SeaMonkey is mostly a shell build on top.

Later versions improve performance but most commercial websites nowadays are just plain garbage and pull in javascript and ads from x sites. They are unusable without an ad- and a script blocker.

Klar has blockers build in. Don't know about iron.

Comment 5

[mhonline]

@Frank:
closed? really?
with these excuses?
wow!
I guess you better ask someone knowing more programming and project-lead before taking decisions like this. 
m.

Comment 6

[Frank-Rainer Grahl (:frg)]

> I guess you better ask someone knowing more programming and project-lead before taking decisions like this.

Sure. I can open 20 bugs a day for badly designed websites and fully know that they will go nowhere. This is all backend stuff and we can't do a thing about it unless try to backport some stuff when a fix is available upstream. You can open a core bug if you want.
Todays we is unusable without a script and ad blocker. For the near future we for sure won't put any of this functionality in SeaMonkey. That is what extensions are for.
The next planned version 2.57 should be faster but it is not yet ready yet.