Bugzilla – Bug 1214899
seamonkey 2.53.14 crashes with segmentation fault on specific website
Last modified: 2023-09-13 11:32:43 UTC
[I previously reported to https://bugzilla.mozilla.org/show_bug.cgi?id=1850915, but it was "resolved" with "2.53.14 is outdated and we do not support the distribution version. Please open a ticket with the distribution."] --- trying to load the page https://www.srf.ch/audio/radio-srf-3-live-hoeren immediately after loading the page, seamonkey crashes with /usr/bin/seamonkey: Zeile 140: 16509 Speicherzugriffsfehler (Speicherabzug geschrieben) $MOZ_PROGRAM "$@" The crash only occurs on this specific site, as far as seen by now The page loads normal in Firefox 115.1.0esr and worked normal in seamonkey during years until the upgrade from OpenSuse 15.3 ->15.4 -> 15.5 I tried with a new empty seamonkey profile, but the error remains.
# zypper lr -d | grep zill ... http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.5/ | # zypper se -sx seamonkey ... S | Name | Type | Version | Arch | Repository --+-----------+------------+--------------------+--------+----------- | seamonkey | package | 2.53.17-lp155.1.8 | x86_64 | Mozilla | seamonkey | package | 2.53.14-bp155.1.14 | x86_64 | OSS | seamonkey | srcpackage | 2.53.17-lp155.1.8 | noarch | Mozilla # The current SM version available from the above BS repo does not crash here using that URL.
I can confirm that version 2.53.17 from http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.5/ does not crash on that site. But with OS 15.5 and the "normal" repo comes 2.53.14 which shows the crash described.
(In reply to Daniel Bauer from comment #2) > I can confirm that version 2.53.17 from > http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.5/ does > not crash on that site. > > But with OS 15.5 and the "normal" repo comes 2.53.14 which shows the crash > described. So this bug essentially amounts to "please publish SeaMonkey 2.53.17 in the main Leap 15.5 repositories". I pushed the update back on 4 August but due to some hold-ups it's only today that the final(?) review has been approved. So hopefully we just need to wait a few hours now for the repository to be updated. *** This bug has been marked as a duplicate of bug 1213986 ***