Tristan Miller wrote:
> Greetings.
>
> On 2023-04-02 11:31, Don Spam's Reckless Son wrote:
>> To summarise,
>> - Ant is having this problem under Windows, with two different SM levels
>> - Tristan is having this problem under Linux, multiple SM levels.
>
>
> I'm now able to reproduce the problem fairly consistently -- namely, by
> watching YouTube videos.  The interesting thing is that it's not just
> SeaMonkey that crashes when I try to watch a video, but also Firefox,
> Chromium, and Google Chrome.  So my problem definitely isn't specific to
> SeaMonkey.  All of these browsers end up segfaulting.  I imagine the problem
> must be either in some media codec that all the browsers are using, or
> something even lower-level like the X server or the kernel.
>
> Regards,
> Tristan
>

Just make sure you don't use a 2.53.15 compiled with rust >=1.67. This one
will crash. Worked around in 2.53.16.

FRG

frg wrote:
> Tristan Miller wrote:
>> Greetings.
>>
>> On 2023-04-02 11:31, Don Spam's Reckless Son wrote:
>>> To summarise,
>>> - Ant is having this problem under Windows, with two different SM levels
>>> - Tristan is having this problem under Linux, multiple SM levels.
>>
>>
>> I'm now able to reproduce the problem fairly consistently -- namely,
>> by watching YouTube videos.  The interesting thing is that it's not
>> just SeaMonkey that crashes when I try to watch a video, but also
>> Firefox, Chromium, and Google Chrome.  So my problem definitely isn't
>> specific to SeaMonkey.  All of these browsers end up segfaulting.  I
>> imagine the problem must be either in some media codec that all the
>> browsers are using, or something even lower-level like the X server or
>> the kernel.
>>
>> Regards,
>> Tristan
>>
>
> Just make sure you don't use a 2.53.15 compiled with rust >=1.67. This
> one will crash. Worked around in 2.53.16.
>
> FRG

(Tristan knows that, I mailed him a couple of weeks ago in his capacity
as OpenSUSE / Seamonkey packager), he also specifically said that he was
using a newer level of Seamonkey (than 2.53.15).

Memtest?

Don Spam's Reckless Son wrote:
> frg wrote:
>> Tristan Miller wrote:
>>> Greetings.
>>>
>>> On 2023-04-02 11:31, Don Spam's Reckless Son wrote:
>>>> To summarise,
>>>> - Ant is having this problem under Windows, with two different SM levels
>>>> - Tristan is having this problem under Linux, multiple SM levels.
>>>
>>>
>>> I'm now able to reproduce the problem fairly consistently -- namely, by
>>> watching YouTube videos.  The interesting thing is that it's not just
>>> SeaMonkey that crashes when I try to watch a video, but also Firefox,
>>> Chromium, and Google Chrome.  So my problem definitely isn't specific to
>>> SeaMonkey.  All of these browsers end up segfaulting.  I imagine the
>>> problem must be either in some media codec that all the browsers are using,
>>> or something even lower-level like the X server or the kernel.
>>>
>>> Regards,
>>> Tristan
>>>
>>
>> Just make sure you don't use a 2.53.15 compiled with rust >=1.67. This one
>> will crash. Worked around in 2.53.16.
>>
>> FRG
>
> (Tristan knows that, I mailed him a couple of weeks ago in his capacity as
> OpenSUSE / Seamonkey packager), he also specifically said that he was using a
> newer level of Seamonkey (than 2.53.15).
>
> Memtest?

Yeah I thought so but just wasn't sure.

FRG

Greetings.

On 2023-04-05 13:09, Don Spam's Reckless Son wrote:
>> Just make sure you don't use a 2.53.15 compiled with rust >=1.67. This
>> one will crash. Worked around in 2.53.16.
>>
>> FRG
>
> (Tristan knows that, I mailed him a couple of weeks ago in his capacity
> as OpenSUSE / Seamonkey packager), he also specifically said that he was
> using a newer level of Seamonkey (than 2.53.15).
>
> Memtest?

The problem may be, as I've just discovered, that after a few seconds
after bootup, my root partition, which uses BTRFS, becomes read-only.
(This turns out to be causing all sorts of problems, possibly including
the browser crashes.) This behaviour is consistent with a kernel bug
that was reported at
<https://bugzilla.opensuse.org/show_bug.cgi?id=1207231> for version
6.1.3 of the kernel, except that I'm experiencing it with 6.2.8 and
6.2.9. So maybe it's a regression, or maybe I'm experiencing a
different problem with similar symptoms. I want to try installing an
earlier kernel to see if that fixes things, but I can't because, as I
said, my root filesystem becomes read-only shortly after bootup. I also
can't create a rescue boot disk at the moment because I don't have any
software installed that can write an ISO image to a USB drive (and can't
install such software due to the aforementioned read-only issue). I'll
have to wait until I'm back from holiday and can produce a rescue boot
disk with another machine.

I'll also try memtest once I'm able to put it on a bootable USB drive.

Regards,
Tristan

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tristan Miller
Free Software developer, ferret herder, logologist
https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-