1421093 - CRASH on some websites

Status: RESOLVED DUPLICATE of bug 1382358

(SeaMonkey :: General, defect)

Description

[Mike]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171112125346

Steps to reproduce:

Gentoo Linux
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48
Build identifier: 20171123181229

Updated Nvidia-Drivers to version 387.22:0


Actual results:

The update started crashing both Seamonkey-2.48 (source) and Firefox-Bin-52.5.0 (binary) on specific web sites.  Newegg and Reddit for sure.

I located this bug #1382358 related to Firefox. Updating Firefox-Bin to version 57.0 solved the Firefox issue as the problem was fixed in the Firefox-56 release.

I am unable to locate such a bug report or patch for Seamonkey-2.48 that may resolve it's issue.


Expected results:

I am always hopeful for smooth updates, but these things happen.

Comment 1

[Rainer Bielefeld]

No obvious DUPs found with <https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DUPs1421093&sharer_id=41036&list_id=13904338>

@Reporter, please:
a) Contribute a problem related step by step instruction containing every 
   key press and every mouse click how to reproduce your problem due to 
   <https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines>
   (similar to report in Bug 1139273)
b) Attach screenshots with comments if you believe that that might explain the 
   problem better than a text comment. Best way is to insert your screenshots
   into a OOo or LibreOffice DRAW document and to add comments 
   that explain what you want to show (attach .png or PDF from source document)
c) add information 
c1) concerning your Operating System (Version, Distribution, Language)
c2) concerning your SM localization (UI language, Locale setting)
c3) SM settings that might be related to your problems 
    May be you should attach a copy of menu 
   'Help → Trouble shooting information”' as a text document
c4) how you launch SM (Double click on document? console? …)
c5) Whether problem persists in Safe Mode without add-ons
c6) Whether problem persists with blank new profile
c7) everything else crossing your mind after you read linked texts
d)  An URL for a web page where you observe the problem.
e) Complete list of settings you used due to recommendations of Thunderbird
  (what work) and all differences in settings due to recommendation of SeaMonkey
f) from which version did you update?
g) If your problem is a that SeaMonkey crahses please contribute at least 1 
   crash report ID; you find it ir you type “about:crashes” as URL into the 
   location bar and visit that page

Please answer without citing, simply start your reply like
a): <answer>

Comment 2

[Phoenix]

What about 2.49.1?

Comment 3

[Frank-Rainer Grahl (:frg)]

Yes. 2.48 is outdated. Please update to 2.49.1 and post a crash id  if you still experience a problem with specific websites.

Comment 4

[Mike]

(In reply to Rainer Bielefeld from comment #1)
> No obvious DUPs found with
> <https://bugzilla.mozilla.org/buglist.
> cgi?cmdtype=dorem&remaction=run&namedcmd=DUPs1421093&sharer_id=41036&list_id=
> 13904338>
> 
OS: Gentoo Linux
System Info:  Portage 2.3.13 (python 2.7.14-final-0, default/linux/amd64/13.0, gcc-6.4.0, glibc-2.25-r9, 4.12.12-gentoo x86_64)
System uname: Linux-4.12.12-gentoo-x86_64-AMD_FX-tm-8350_Eight-Core_Processor-with-gentoo-2.4.1

Locale: LANG=en_US.utf8

Steps how to reproduce with Seamonkey-2.48 Build: 20171123181229 on 64bit Gentoo Linux.

1. emerge www-client/seamonkey-2.48 (64bit compiled from source)

Seamonkey source build info:
[ebuild   R    ] www-client/seamonkey-2.48::gentoo  USE="calendar chatzilla crypt dbus gmp-autoupdate ipc jemalloc pulseaudio roaming skia startup-notification -custom-cflags -custom-optimization -debug -gtk3 -jack -minimal (-neon) (-selinux) (-system-cairo) -system-harfbuzz -system-icu -system-jpeg -system-libevent -system-libvpx -system-sqlite {-test} -wifi" L10N="-cs -de -en-GB -es-AR -es-ES -fr -hu -it -ja -lt -nl -pl -pt-PT -ru -sk -sv -zh-CN -zh-TW" 0 KiB

2. Open seamonkey search and surf the web, seamonkey works flawlessly and preforms well.

3. Update to the latest stable linux nvidia-drivers-387.22

4. Open seamonkey and "type" www.newegg.com into location bar, hit "enter" key, site begins to load then seamonkey just shuts down. No log errors or messages are reported any where on the system. Only the browser portion of seamonkey suffers this crash and only on some web sites. Most web sites load without any problems.

I am unable to find any crash report or ID on my system for seamonkey
"about:crashes" yields "The URL is not valid and cannot be loaded."
Problem persists with or without add-ons enabled.
Seamonkey-2.48 worked properly before updating my graphics drivers.

5. Open Firefox so I could access www.newegg.com, site begins to load then firefox crashes. However firefox dumps a crash report.

	MozCrashReason: MOZ_CRASH(GFX: Unexpected GLSL version.)
	Notes: NAME=GentooFP(D00-L1000-W00000000-T0000) OpenGL: NVIDIA Corporation -- GeForce GTX 980/PCIe/SSE2 -- 4.6.0 NVIDIA 387.22 -- 		texture_from_pixmap
	WebGL? libGL.so.1? libGL.so.1+ GL Context? GL Context+ WebGL+
	ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
	ProductName: Firefox
ReleaseChannel: esr

Firefox Crash: ID https://crash-stats.mozilla.com/report/index/bp-ed16737b-787b-4a03-83bb-d0ffe0171126

6. Searching google for clues lead me to https://hg.mozilla.org/integration/mozilla-inbound/rev/4a5185552a07 which in turn lead me to bug #1382358

7. Seamonkey and firefox both functioned properly before I updated my graphics drivers and both were crashing at exactly the same locations and sites after the update. I reasoned that Seamonkey (using the firefox backend) was crashing for the exact reason as firefox.

8. Googling and searching https://bugzilla.mozilla.org for "seamonkey" bugs or patches related to this crash led me straight back to the firefox reports I had already found.

9. (As a Test) Update Firefox to version 57.0 (prebuilt 64bit binary install) from Gentoo's testing branch. Problem is gone and browser now opens sites where it crashed before.

Comment 5

[Mike]

Other Gentoo users, using Firefox have also been having the same problems.  Short discussion on the forums at https://forums.gentoo.org/viewtopic.php?p=8147630#8147630

I must be the only person using Seamonkey in Gentoo as my main browser suite.

Comment 6

[Frank-Rainer Grahl (:frg)]

Well it is only a one liner. As stated 2.48 is outdated. There will be no official fix for this one. Please try the official 2.49.1, see if it also crashes and provide a crash id. If you compile yourself just change the line from MOZ_CRASH to MOZ_ASSERT.

We can put this into 2.49.2 then but if it affects 52.5 ESR too request an uplift to the esr branch in bug 1382358.

FRG

Comment 7

[Mike]

(In reply to Frank-Rainer Grahl (:frg) from comment #6)
> Well it is only a one liner. As stated 2.48 is outdated. There will be no
> official fix for this one. Please try the official 2.49.1, see if it also
> crashes and provide a crash id. If you compile yourself just change the line
> from MOZ_CRASH to MOZ_ASSERT.
> 
> We can put this into 2.49.2 then but if it affects 52.5 ESR too request an
> uplift to the esr branch in bug 1382358.
> 
> FRG

Per your request I installed Seamonkey-2.49.1 from the Gentoo ~testing branch. I installed via seamonkey-bin (prebuilt 64bit binary) because...
1. It allows me to run both version 2.48 and version 2.49.1 side by side.
2. The Bug tracking system works in the binary where it doesn't when complied from source. (Probably due to gnome dependency problems.) I don't use the Gnome DE   
3. Building Seamonkey from source through Gentoo's package manager (portage) takes a lot of time and system resources.

Seamonkey build info:
Calculating dependencies... done!
[ebuild   R   ~] www-client/seamonkey-bin-2.49.1_rc2::gentoo  USE="ffmpeg pulseaudio startup-notification" L10N="-cs -de -en-GB -es-AR -es-ES -fr -hu -it -ja -lt -nl -pl -pt-PT -ru -sk -sv -zh-CN -zh-TW" 0 KiB

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
Build identifier: 20171004015703

After installing Seamonkey-2.49.1:

1. Open seamonkey-bin-2.49.1 and "type" www.newegg.com into location bar, hit "enter" key, site begins to load then seamonkey just shuts down but now dumps a crash report.

Seamonkey Crash ID: https://crash-stats.mozilla.com/report/index/ffa42b4e-0df2-4e60-928a-9189d0171129

As I reasoned before the crash is identical to the firefox crash.

From what I have read in the reports this will/may affect any system using any version of firefox less than 56 (on linux at least, I haven't tested Seamonkey in Windows) if they have nvidia-drivers  =>381.26.13 installed, their hardware supports opengl 4.6.0 and GLSL 4.60 and they happen upon a website that will cause the crash. (To many ducks, sounds kinda rare!!!)

I compile 99.9% of all my applications and system files. Gentoo is a source based distro. I can't just change the code because the package manager will spot a check sum diff and choke. I would have to compile outside of the packager manager which could potentially introduce other problems. I need to patch my current version through epatch via the package manager.

I will report this to the Gentoo Dev's and reference this bug in hopes they will produce a patch to solve the problem in both Firefox and Seamonkey.

Current Gentoo Stable Branch:
Firefox-52.4.0 64bit
Seamonkey-2.48 64bit

Comment 8

[Frank-Rainer Grahl (:frg)]

I asked for an uplift. If it is not granted or comes too late we will likely put it in a 2.49.2 source branch.

Comment 9

[Mike]

Seamonkey is an extremely important and useful tool I count on daily.  Most Linux distros lag behind application development when it comes to stabilizing packages. Thanks to all the help and info here and a lot of research on my part I was able to create a patch I could use with Gentoo's package manager.  After applying the patch and recompiling Seamonkey-2.48 I can confirm the bug is longer present. Sites that crashed the browser before now load and function normally.

Thanks

Comment 10

[Frank-Rainer Grahl (:frg)]

Bug 1382358 was uplifted so can close this one as a duplicate.

Comment 11

[Frank-Rainer Grahl (:frg)]

Will be fixed in 2.49.2