Open Bug 1780322 Opened 2 years ago Updated 2 years ago

SeaMonkey 2.53.13 crashes often (regression from 2.53.12)

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.53 Branch
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: commander4bugs, Unassigned)

Details

Attachments

(1 file)

51.28 KB, application/json
Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.12

Steps to reproduce:

It seems that the 2.53.13 release is much worse that the previous 2.53.12 release.
The new release seems to be noticeably slower on many pages. Furthermore,
the browser crashes more often even from a clean start and a single page open.

The 3 sites, where I see this happening very consistently are these (there could be others):

Sorry, I do not have a public file for Google Spreadsheets. Most likely,
any table will cause problems. The one I use is a very trivial table,
no fancy charts or scripts. Just a small table with a few columns
and about 100 rows.

Actual results:

The browser is noticeably slower, often crashes. Sometimes the browser
shows clear signs of the screen corruption (and crashes soon).

Expected results:

The pages should open and work as expected (and were in 2.53.12).

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.12

This indicates the x86 version running on Windows 10 x86. If this is the case you are probably running out of memory. The mentioned sites or at least google and yahoo are known memory hogs and the latest SeaMonkey version allocates more in some cases to be able to display a site correctly. If you have not installed an ad- or script blocker do so.

In any case this bug does not contain enough information. Please add at least a crash id and the output from about:support

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

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.12

This indicates the x86 version running on Windows 10 x86.

Windows NT 6.1 is Windows 7, not 10 ;) And yes, it is a 32-bit version.

If this is the case you are probably running out of memory.

Most definitely not. For example, after opening the PYPL stock chart, the SeaMonkey process
is taking only 330 MB of RAM. And I have 4 GB. The memory limit is not even close, not even close
to the swap file.

The mentioned sites or at least google and yahoo are known memory hogs
and the latest SeaMonkey version allocates more in some cases to be able
to display a site correctly.

If this were just something out of the blue and random, I would buy this argument.
In this case, the previous version 2.53.12 works just fine for any of these sites.
I visit them often. As soon as I installed 2.53.13, boom. Google Spreadsheets - can not even open.
The same story for E-Trade. Yahoo finance charts - a crash within seconds.
As soon as I downgraded back to 2.53.12, I can open every single one of these
sites. Without even restarting the operating system. This clearly indicates a regression,
not a memory problem. Unless, of cause 2.53.13 suddenly wants 10 times the memory
to open these sites. Which would be a regression by itself :)

If you have not installed an ad- or script blocker do so.

I do. ublock Origin. Nowadays, it is not possible to browse the web without it .

Please add at least a crash id

about:support shows these reports:

Crash Reports for the Last 3 Days
bp-9461f599-a4f7-4042-84a4-c86290220720
bp-001e8ef9-3700-429e-89eb-00c130220720
bp-91e1cdba-2408-4f00-a036-48fe00220720
bp-1d43b5c6-c48f-4a37-a3da-6a1530220720
bp-8702352c-b311-4881-87b1-e26510220720

I do not know which one is from which day. You should look only at the ones
yesterday (July 19th), when I had 2.53.13 installed.

and the output from about:support

Added as an attachment to this bug.

Attached file support.json

Crash stats is down at the moment. Need to ask ewong. Your urls point to the mozilla server. Need to check if we format them correctly.

In any case I am unable to reproduce. in a vm. Yahoo loads but begins to lag later when I start enabling script sites via NoScript. But this is in a vm and it never crashed just started to eat the cpu when playing video. I had problemes with Nvidia 3.78 drivers and 3.91 is not far away. Unfortunately the latest ones available for x86. Tray disabling hardware acceleration. If this doesn't help need to wait for ewong. 2.53.13 has some later graphics libraries included which might explain problems with older drivers. But just a guess.

x86 is on the way out. I browsed a bit and played some media today and got a 3 GB ram footprint. I would upgrade ram and use a Windows x64 version. At least for me no unexplained crashes for a long time.

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

Your urls point to the mozilla server. Need to check if we format them correctly.

I simply copy-pasted them from the about:support page.

Tray disabling hardware acceleration.

OK, disable. Let's see if this helps.

If this doesn't help need to wait for ewong. 2.53.13 has some later graphics libraries
included which might explain problems with older drivers. But just a guess.

Let me know when the crash server starts working. If you want, I can try to reproduce
the crashes and give you a new crash ID.

x86 is on the way out. I browsed a bit and played some media today and got a 3 GB ram
footprint. I would upgrade ram and use a Windows x64 version. At least for me no unexplained
crashes for a long time.

Firefox on the same system with the same resources works just fine. No crashes, no 100% CPU
usage. So, it can't be just memory or "bitness". In fact, even in SeaMonkey the memory is not really
a problem. If I open a million tabs, sure, it starts eating a lot of RAM. But I do not do that.
Even with very moderate browsing it tends to go into 100% CPU or flat out crash.
Every time the memory is only a few hundreds of MB.

For what it is worth. I bought a Thinkpad T430s and it had Optimus and an NVS5200M in. Needed to use 3.91 drivers in Windows 7 x64 and experienced the exact same problem after playing some youtube videos. Window experiences graphics corruption after about 10-15 minutes. Switching to the Intel HD 4000 or using a W530 with 4.26 drivers = no problem. My desktop 1070Ti is fine also so I am inclined to close this as a driver problem. Later Firefox versions now use webrender and a different architecture so might not hit the graphics driver bug. The 3.91 driver is blacklisted for advanced layers too because of problems.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: