Ant wrote:
> In alt.comp.software.seamonkey Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
>> Don Spam's Reckless Son wrote:
>>> Ant wrote:
>>>> Hmm, I had one today. Hmm!
>>>
>>> I was looking at your list of add-ons:
>>>
>>> 1    ublock0@raymondhill.net: 1.16.4.30
>>> 2    expire-history-by-days@bonardo.net: 1.2.0
>>> 3    openwith@darktrojan.net: 6.8.6
>>> 4    {8a6c82a1-f6c9-481a-aae7-c96444c9a754}: 7.1.1
>>> 5    inspector@mozilla.org: 2.0.19
>>> 6    modern@themes.mozilla.org: 2.53.16
>>>
>>> I use "1" myself, "5" and "6" are obviously harmless (I use the Default
>>> theme myself).
>>> That leaves "2", "3" and "4" (wtf is "4"?)
>>> You could probably disable "2" for a while and see what happens, but
>>> comparing your list with Tristan's could also possibly be helpful.
>>> Disabling "3" would be a problem for you, as for "4" - really, wtf is it?
>>>
>>> The way my Seamonkey was generated, I don't have that crash information
>>> anyway (no about:crashes at all).  If it was possible there would have
>>> been enough of them from when I had 2.53.15.
>
>> 8a6c82a1-f6c9-481a-aae7-c96444c9a754 appears to be the ID of the PrefBar
>> extension. That doesn't seem to be available from
>> <https://addons.thunderbird.net/seamonkey/>, and I'm not sure where the
>> official download for it is, but
>> <http://prefbar.tuxfamily.org/archive.html> says:
>>> Please be aware, that PrefBar is no longer maintained! It is not recommend to install any of these versions!
>>> They most probably don't work well with current versions of SeaMonkey and they won't install at all on Firefox 57 and above!
>
>> 7.1.1 is the latest version listed, released in 2017 so pretty old. I'm
>> not sure why it would have suddenly started causing problems without
>> having updated SeaMonkey, but could be worth seeing if disabling it
>> stops the crashes. Maybe a configuration change could have triggered
>> something that wasn't a problem before.
>
> Yeah, PrefBar. Well, I was using it a few weeks ago and before without issues. :/
>

Have not heard back from ewong so can't check the crashes. It sounds system
specific so I would do a memory test and also check the SSD or HDD smart data.
Also see if the video driver got updated. If you have dual Nvidia/Intel
graphics try to run with a different gpu.

expire-history-by-days@bonardo.net is probably not compatible any longer.
Chances are high that you trash you bookmarks history using it. I need to
remove the last remains of the old synchronous bookmarks api soon and then it
will probably stop even pretending to work. Just didn't happen yet because no
time.

FRG

frg <frgrahl@gmx.net> wrote:
> Ant wrote:
> > In alt.comp.software.seamonkey Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
> >> Don Spam's Reckless Son wrote:
> >>> Ant wrote:
> >>>> Hmm, I had one today. Hmm!
> >>>
> >>> I was looking at your list of add-ons:
> >>>
> >>> 1    ublock0@raymondhill.net: 1.16.4.30
> >>> 2    expire-history-by-days@bonardo.net: 1.2.0
> >>> 3    openwith@darktrojan.net: 6.8.6
> >>> 4    {8a6c82a1-f6c9-481a-aae7-c96444c9a754}: 7.1.1
> >>> 5    inspector@mozilla.org: 2.0.19
> >>> 6    modern@themes.mozilla.org: 2.53.16
> >>>
> >>> I use "1" myself, "5" and "6" are obviously harmless (I use the Default
> >>> theme myself).
> >>> That leaves "2", "3" and "4" (wtf is "4"?)
> >>> You could probably disable "2" for a while and see what happens, but
> >>> comparing your list with Tristan's could also possibly be helpful.
> >>> Disabling "3" would be a problem for you, as for "4" - really, wtf is it?
> >>>
> >>> The way my Seamonkey was generated, I don't have that crash information
> >>> anyway (no about:crashes at all).  If it was possible there would have
> >>> been enough of them from when I had 2.53.15.
> >
> >> 8a6c82a1-f6c9-481a-aae7-c96444c9a754 appears to be the ID of the PrefBar
> >> extension. That doesn't seem to be available from
> >> <https://addons.thunderbird.net/seamonkey/>, and I'm not sure where the
> >> official download for it is, but
> >> <http://prefbar.tuxfamily.org/archive.html> says:
> >>> Please be aware, that PrefBar is no longer maintained! It is not recommend to install any of these versions!
> >>> They most probably don't work well with current versions of SeaMonkey and they won't install at all on Firefox 57 and above!
> >
> >> 7.1.1 is the latest version listed, released in 2017 so pretty old. I'm
> >> not sure why it would have suddenly started causing problems without
> >> having updated SeaMonkey, but could be worth seeing if disabling it
> >> stops the crashes. Maybe a configuration change could have triggered
> >> something that wasn't a problem before.
> >
> > Yeah, PrefBar. Well, I was using it a few weeks ago and before without issues. :/
> >

> Have not heard back from ewong so can't check the crashes. It sounds system
> specific so I would do a memory test and also check the SSD or HDD smart data.

I doubt it is the drive since other programs are fine.

> Also see if the video driver got updated. If you have dual Nvidia/Intel
> graphics try to run with a different gpu.

Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
of VRAM) recently. Wouldn't my other programs be having issues too?

> expire-history-by-days@bonardo.net is probably not compatible any longer.
> Chances are high that you trash you bookmarks history using it. I need to
> remove the last remains of the old synchronous bookmarks api soon and then it
> will probably stop even pretending to work. Just didn't happen yet because no
> time.

Ooh, good call. Let me disable that extension to see if that makes a
difference. Not an urgent extension. Is there even an updated or a
replacement?

--
"On the evening of that first day of the week, when the disciples were together, with the doors locked for fear of the Jews, Jesus came and stood among them and said, "Peace be with you!" After he said this, he showed them his hands and side. The disciples were overjoyed when they saw the Lord." --John 20:19. WB is 100! HTTP 404 error not found day!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
>> It sounds system
>> specific so I would do a memory test and also check the SSD or HDD smart data.
> I doubt it is the drive since other programs are fine.
>

I recently had a failure of compressing my inbox. Seems my SSD is
returning a verify error on the partition where my profiles live. Now
have to install windows to check the drive in detail, update the
firmware and find out if I have to send it back.
Other then my inbox sorta breaking (thank god for multiple backups, I
recovered everything except maybe one message) when compacting
everything seems fine on the SSD.
Problems can be subtle
Dave

Ant wrote:
> frg <frgrahl@gmx.net> wrote:
>> Have not heard back from ewong so can't check the crashes. It sounds system
>> specific so I would do a memory test and also check the SSD or HDD smart data.
>
> I doubt it is the drive since other programs are fine.

It could just be that SeaMonkey just happens to be using a faulty sector
on the disk. As with memory problems, it doesn't necessarily affect all
applications equally. Some applications do things that are more likely
to be affected by faults (I seem to recall compiling the Linux kernel
being considered a good stress-test for a system), and some are just
unlucky to happen to be using the faulty part.

>> Also see if the video driver got updated. If you have dual Nvidia/Intel
>> graphics try to run with a different gpu.
>
> Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
> of VRAM) recently. Wouldn't my other programs be having issues too?

Again, it could be that SeaMonkey uses the graphics card in ways that
the other applications you use don't. Tristan mentioned in another
thread that YouTube is causing multiple browsers to crash for him, which
could be related to decoding the video streams in the graphics hardware
(maybe even something specific in the streams produced by YouTube that
triggers a bug in the graphics driver). I don't even know whether you
and Tristan are getting the same crashes for the same reason though, but
such things are plausible.

>> expire-history-by-days@bonardo.net is probably not compatible any longer.
>> Chances are high that you trash you bookmarks history using it. I need to
>> remove the last remains of the old synchronous bookmarks api soon and then it
>> will probably stop even pretending to work. Just didn't happen yet because no
>> time.
>
> Ooh, good call. Let me disable that extension to see if that makes a
> difference. Not an urgent extension. Is there even an updated or a
> replacement?

Definitely worth disabling all the extensions you can, even if just for
a week or two to see if it makes any difference. Similar with my
earlier comments about PrefBar - it seems unlikely that it would have
suddenly started causing problems whether neither SeaMonkey nor PrefBar
have been updated, but still worth a shot. If disabling it doesn't stop
the crashes, it can be re-enabled, but at least it's one more thing
ruled out.

--
Mark.

Dave Yeo <dave.r.yeo@gmail.com> wrote:
> Ant wrote:
> >> It sounds system
> >> specific so I would do a memory test and also check the SSD or HDD smart data.
> > I doubt it is the drive since other programs are fine.
> >

> I recently had a failure of compressing my inbox. Seems my SSD is
> returning a verify error on the partition where my profiles live. Now
> have to install windows to check the drive in detail, update the
> firmware and find out if I have to send it back.
> Other then my inbox sorta breaking (thank god for multiple backups, I
> recovered everything except maybe one message) when compacting
> everything seems fine on the SSD.
> Problems can be subtle
> Dave

How did you get the verify errors with your SSD? I still haven't seen
any of those?

--
"I call to God, and the LORD saves me. Evening, morning and noon I cry out in distress, and he hears my voice." --Psalm 55:16-17. Annual Passover (should I C Ridley Scott's bad 2.5 hrs. Exodus: Gods & Kings?) & (Qingming / Ching Ming) Festival on a Holy hump day!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
> Ant wrote:
> > frg <frgrahl@gmx.net> wrote:
> >> Have not heard back from ewong so can't check the crashes. It sounds system
> >> specific so I would do a memory test and also check the SSD or HDD smart data.
> >
> > I doubt it is the drive since other programs are fine.

> It could just be that SeaMonkey just happens to be using a faulty sector
> on the disk. As with memory problems, it doesn't necessarily affect all
> applications equally. Some applications do things that are more likely
> to be affected by faults (I seem to recall compiling the Linux kernel
> being considered a good stress-test for a system), and some are just
> unlucky to happen to be using the faulty part.

> >> Also see if the video driver got updated. If you have dual Nvidia/Intel
> >> graphics try to run with a different gpu.
> >
> > Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
> > of VRAM) recently. Wouldn't my other programs be having issues too?

> Again, it could be that SeaMonkey uses the graphics card in ways that
> the other applications you use don't. Tristan mentioned in another
> thread that YouTube is causing multiple browsers to crash for him, which
> could be related to decoding the video streams in the graphics hardware
> (maybe even something specific in the streams produced by YouTube that
> triggers a bug in the graphics driver). I don't even know whether you
> and Tristan are getting the same crashes for the same reason though, but
> such things are plausible.

> >> expire-history-by-days@bonardo.net is probably not compatible any longer.
> >> Chances are high that you trash you bookmarks history using it. I need to
> >> remove the last remains of the old synchronous bookmarks api soon and then it
> >> will probably stop even pretending to work. Just didn't happen yet because no
> >> time.
> >
> > Ooh, good call. Let me disable that extension to see if that makes a
> > difference. Not an urgent extension. Is there even an updated or a
> > replacement?

> Definitely worth disabling all the extensions you can, even if just for
> a week or two to see if it makes any difference. Similar with my
> earlier comments about PrefBar - it seems unlikely that it would have
> suddenly started causing problems whether neither SeaMonkey nor PrefBar
> have been updated, but still worth a shot. If disabling it doesn't stop
> the crashes, it can be re-enabled, but at least it's one more thing
> ruled out.

Well, it doesn't seem to be expire history by days extension and even a
newer NVIDIA GeForce driver. I disabled others like DOM Inspector, Open
With, and PrefBar for now.
--
"I call to God, and the LORD saves me. Evening, morning and noon I cry out in distress, and he hears my voice." --Psalm 55:16-17. Annual Passover (should I C Ridley Scott's bad 2.5 hrs. Exodus: Gods & Kings?) & (Qingming / Ching Ming) Festival on a Holy hump day!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
> Ant wrote:
> > frg <frgrahl@gmx.net> wrote:
> >> Have not heard back from ewong so can't check the crashes. It sounds system
> >> specific so I would do a memory test and also check the SSD or HDD smart data.
> >
> > I doubt it is the drive since other programs are fine.

> It could just be that SeaMonkey just happens to be using a faulty sector
> on the disk. As with memory problems, it doesn't necessarily affect all
> applications equally. Some applications do things that are more likely
> to be affected by faults (I seem to recall compiling the Linux kernel
> being considered a good stress-test for a system), and some are just
> unlucky to happen to be using the faulty part.

> >> Also see if the video driver got updated. If you have dual Nvidia/Intel
> >> graphics try to run with a different gpu.
> >
> > Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
> > of VRAM) recently. Wouldn't my other programs be having issues too?

> Again, it could be that SeaMonkey uses the graphics card in ways that
> the other applications you use don't. Tristan mentioned in another
> thread that YouTube is causing multiple browsers to crash for him, which
> could be related to decoding the video streams in the graphics hardware
> (maybe even something specific in the streams produced by YouTube that
> triggers a bug in the graphics driver). I don't even know whether you
> and Tristan are getting the same crashes for the same reason though, but
> such things are plausible.

> >> expire-history-by-days@bonardo.net is probably not compatible any longer.
> >> Chances are high that you trash you bookmarks history using it. I need to
> >> remove the last remains of the old synchronous bookmarks api soon and then it
> >> will probably stop even pretending to work. Just didn't happen yet because no
> >> time.
> >
> > Ooh, good call. Let me disable that extension to see if that makes a
> > difference. Not an urgent extension. Is there even an updated or a
> > replacement?

> Definitely worth disabling all the extensions you can, even if just for
> a week or two to see if it makes any difference. Similar with my
> earlier comments about PrefBar - it seems unlikely that it would have
> suddenly started causing problems whether neither SeaMonkey nor PrefBar
> have been updated, but still worth a shot. If disabling it doesn't stop
> the crashes, it can be re-enabled, but at least it's one more thing
> ruled out.

Also, do I assume disabling extensions is OK? I hope I don't have to remove them.
--
"I call to God, and the LORD saves me. Evening, morning and noon I cry out in distress, and he hears my voice." --Psalm 55:16-17. Annual Passover (should I C Ridley Scott's bad 2.5 hrs. Exodus: Gods & Kings?) & (Qingming / Ching Ming) Festival on a Holy hump day!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant <ant@zimage.comant> wrote:
> Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
> > Ant wrote:
> > > frg <frgrahl@gmx.net> wrote:
> > >> Have not heard back from ewong so can't check the crashes. It sounds system
> > >> specific so I would do a memory test and also check the SSD or HDD smart data.
> > >
> > > I doubt it is the drive since other programs are fine.

> > It could just be that SeaMonkey just happens to be using a faulty sector
> > on the disk. As with memory problems, it doesn't necessarily affect all
> > applications equally. Some applications do things that are more likely
> > to be affected by faults (I seem to recall compiling the Linux kernel
> > being considered a good stress-test for a system), and some are just
> > unlucky to happen to be using the faulty part.

> > >> Also see if the video driver got updated. If you have dual Nvidia/Intel
> > >> graphics try to run with a different gpu.
> > >
> > > Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
> > > of VRAM) recently. Wouldn't my other programs be having issues too?

> > Again, it could be that SeaMonkey uses the graphics card in ways that
> > the other applications you use don't. Tristan mentioned in another
> > thread that YouTube is causing multiple browsers to crash for him, which
> > could be related to decoding the video streams in the graphics hardware
> > (maybe even something specific in the streams produced by YouTube that
> > triggers a bug in the graphics driver). I don't even know whether you
> > and Tristan are getting the same crashes for the same reason though, but
> > such things are plausible.

> > >> expire-history-by-days@bonardo.net is probably not compatible any longer.
> > >> Chances are high that you trash you bookmarks history using it. I need to
> > >> remove the last remains of the old synchronous bookmarks api soon and then it
> > >> will probably stop even pretending to work. Just didn't happen yet because no
> > >> time.
> > >
> > > Ooh, good call. Let me disable that extension to see if that makes a
> > > difference. Not an urgent extension. Is there even an updated or a
> > > replacement?

> > Definitely worth disabling all the extensions you can, even if just for
> > a week or two to see if it makes any difference. Similar with my
> > earlier comments about PrefBar - it seems unlikely that it would have
> > suddenly started causing problems whether neither SeaMonkey nor PrefBar
> > have been updated, but still worth a shot. If disabling it doesn't stop
> > the crashes, it can be re-enabled, but at least it's one more thing
> > ruled out.

> Also, do I assume disabling extensions is OK? I hope I don't have to remove them.

Crash again! https://crash-reports-test.seamonkey-project.org/report/index/bp-d769fb54-5b07-417e-8652-a70b40230405

I only had these on:

ublock0@raymondhill.net: 1.16.4.30
modern@themes.mozilla.org: 2.53.16

I think I will go back to plain theme. I'd hate to run without uBlock
extension so I will just uninstall and reinstall it.

--
"I call to God, and the LORD saves me. Evening, morning and noon I cry out in distress, and he hears my voice." --Psalm 55:16-17. Annual Passover (should I C Ridley Scott's bad 2.5 hrs. Exodus: Gods & Kings?) & (Qingming / Ching Ming) Festival on a Holy hump day!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
> Dave Yeo <dave.r.yeo@gmail.com> wrote:
>> Ant wrote:
>>>> It sounds system
>>>> specific so I would do a memory test and also check the SSD or HDD smart data.
>>> I doubt it is the drive since other programs are fine.
>>>
>> I recently had a failure of compressing my inbox. Seems my SSD is
>> returning a verify error on the partition where my profiles live. Now
>> have to install windows to check the drive in detail, update the
>> firmware and find out if I have to send it back.
>> Other then my inbox sorta breaking (thank god for multiple backups, I
>> recovered everything except maybe one message) when compacting
>> everything seems fine on the SSD.
>> Problems can be subtle
>> Dave
> How did you get the verify errors with your SSD? I still haven't seen
> any of those?

Doing a long format, JFS file system on OS/2, got output like

Internal error: devices.c(532): Verify error 21 (NOT_READY)
Internal error: devices.c(532): Verify error 21 (NOT_READY)

No blocks were marked bad or such
Dave

Ant wrote:
> Ant <ant@zimage.comant> wrote:
>> Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
>>> Ant wrote:
>>>> frg <frgrahl@gmx.net> wrote:
>>>>> Have not heard back from ewong so can't check the crashes. It sounds system
>>>>> specific so I would do a memory test and also check the SSD or HDD smart data.
>>>>
>>>> I doubt it is the drive since other programs are fine.
>
>>> It could just be that SeaMonkey just happens to be using a faulty sector
>>> on the disk. As with memory problems, it doesn't necessarily affect all
>>> applications equally. Some applications do things that are more likely
>>> to be affected by faults (I seem to recall compiling the Linux kernel
>>> being considered a good stress-test for a system), and some are just
>>> unlucky to happen to be using the faulty part.
>
>>>>> Also see if the video driver got updated. If you have dual Nvidia/Intel
>>>>> graphics try to run with a different gpu.
>>>>
>>>> Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
>>>> of VRAM) recently. Wouldn't my other programs be having issues too?
>
>>> Again, it could be that SeaMonkey uses the graphics card in ways that
>>> the other applications you use don't. Tristan mentioned in another
>>> thread that YouTube is causing multiple browsers to crash for him, which
>>> could be related to decoding the video streams in the graphics hardware
>>> (maybe even something specific in the streams produced by YouTube that
>>> triggers a bug in the graphics driver). I don't even know whether you
>>> and Tristan are getting the same crashes for the same reason though, but
>>> such things are plausible.
>
>>>>> expire-history-by-days@bonardo.net is probably not compatible any longer.
>>>>> Chances are high that you trash you bookmarks history using it. I need to
>>>>> remove the last remains of the old synchronous bookmarks api soon and then it
>>>>> will probably stop even pretending to work. Just didn't happen yet because no
>>>>> time.
>>>>
>>>> Ooh, good call. Let me disable that extension to see if that makes a
>>>> difference. Not an urgent extension. Is there even an updated or a
>>>> replacement?
>
>>> Definitely worth disabling all the extensions you can, even if just for
>>> a week or two to see if it makes any difference. Similar with my
>>> earlier comments about PrefBar - it seems unlikely that it would have
>>> suddenly started causing problems whether neither SeaMonkey nor PrefBar
>>> have been updated, but still worth a shot. If disabling it doesn't stop
>>> the crashes, it can be re-enabled, but at least it's one more thing
>>> ruled out.
>
>> Also, do I assume disabling extensions is OK? I hope I don't have to remove them.
>
> Crash again! https://crash-reports-test.seamonkey-project.org/report/index/bp-d769fb54-5b07-417e-8652-a70b40230405
>
> I only had these on:
>
> ublock0@raymondhill.net: 1.16.4.30
> modern@themes.mozilla.org: 2.53.16
>
> I think I will go back to plain theme. I'd hate to run without uBlock
> extension so I will just uninstall and reinstall it.
>

I am running uBlock all the time. Should not cause trouble. Same for the
bundled extensions.

FRG

FRG

Dave Yeo <dave.r.yeo@gmail.com> wrote:
> Ant wrote:
> > Dave Yeo <dave.r.yeo@gmail.com> wrote:
> >> Ant wrote:
> >>>> It sounds system
> >>>> specific so I would do a memory test and also check the SSD or HDD smart data.
> >>> I doubt it is the drive since other programs are fine.
> >>>
> >> I recently had a failure of compressing my inbox. Seems my SSD is
> >> returning a verify error on the partition where my profiles live. Now
> >> have to install windows to check the drive in detail, update the
> >> firmware and find out if I have to send it back.
> >> Other then my inbox sorta breaking (thank god for multiple backups, I
> >> recovered everything except maybe one message) when compacting
> >> everything seems fine on the SSD.
> >> Problems can be subtle
> >> Dave
> > How did you get the verify errors with your SSD? I still haven't seen
> > any of those?

> Doing a long format, JFS file system on OS/2, got output like

> Internal error: devices.c(532): Verify error 21 (NOT_READY)
> Internal error: devices.c(532): Verify error 21 (NOT_READY)

> No blocks were marked bad or such
> Dave

Wow, old OS/2?!
--
"Dear friends, I urge you, as aliens and strangers in the world, to abstain from sinful desires, which war against your soul." --1 Peter 2:11. RIP, ext. Seagate 5 TB portable HDD (Model: SRD0NF1)? :( GM(aundy) & TGIGFE on a Holy wk. :)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

frg <frgrahl@gmx.net> wrote:
> Ant wrote:
> > Ant <ant@zimage.comant> wrote:
> >> Mark Bourne <nntp.mbourne@spamgourmet.com> wrote:
> >>> Ant wrote:
> >>>> frg <frgrahl@gmx.net> wrote:
> >>>>> Have not heard back from ewong so can't check the crashes. It sounds system
> >>>>> specific so I would do a memory test and also check the SSD or HDD smart data.
> >>>>
> >>>> I doubt it is the drive since other programs are fine.
> >
> >>> It could just be that SeaMonkey just happens to be using a faulty sector
> >>> on the disk. As with memory problems, it doesn't necessarily affect all
> >>> applications equally. Some applications do things that are more likely
> >>> to be affected by faults (I seem to recall compiling the Linux kernel
> >>> being considered a good stress-test for a system), and some are just
> >>> unlucky to happen to be using the faulty part.
> >
> >>>>> Also see if the video driver got updated. If you have dual Nvidia/Intel
> >>>>> graphics try to run with a different gpu.
> >>>>
> >>>> Hmm, maybe. I did update my NVIDIA drivers for my GeForce 750 GTX (2 GB
> >>>> of VRAM) recently. Wouldn't my other programs be having issues too?
> >
> >>> Again, it could be that SeaMonkey uses the graphics card in ways that
> >>> the other applications you use don't. Tristan mentioned in another
> >>> thread that YouTube is causing multiple browsers to crash for him, which
> >>> could be related to decoding the video streams in the graphics hardware
> >>> (maybe even something specific in the streams produced by YouTube that
> >>> triggers a bug in the graphics driver). I don't even know whether you
> >>> and Tristan are getting the same crashes for the same reason though, but
> >>> such things are plausible.
> >
> >>>>> expire-history-by-days@bonardo.net is probably not compatible any longer.
> >>>>> Chances are high that you trash you bookmarks history using it. I need to
> >>>>> remove the last remains of the old synchronous bookmarks api soon and then it
> >>>>> will probably stop even pretending to work. Just didn't happen yet because no
> >>>>> time.
> >>>>
> >>>> Ooh, good call. Let me disable that extension to see if that makes a
> >>>> difference. Not an urgent extension. Is there even an updated or a
> >>>> replacement?
> >
> >>> Definitely worth disabling all the extensions you can, even if just for
> >>> a week or two to see if it makes any difference. Similar with my
> >>> earlier comments about PrefBar - it seems unlikely that it would have
> >>> suddenly started causing problems whether neither SeaMonkey nor PrefBar
> >>> have been updated, but still worth a shot. If disabling it doesn't stop
> >>> the crashes, it can be re-enabled, but at least it's one more thing
> >>> ruled out.
> >
> >> Also, do I assume disabling extensions is OK? I hope I don't have to remove them.
> >
> > Crash again! https://crash-reports-test.seamonkey-project.org/report/index/bp-d769fb54-5b07-417e-8652-a70b40230405
> >
> > I only had these on:
> >
> > ublock0@raymondhill.net: 1.16.4.30
> > modern@themes.mozilla.org: 2.53.16
> >
> > I think I will go back to plain theme. I'd hate to run without uBlock
> > extension so I will just uninstall and reinstall it.
> >

> I am running uBlock all the time. Should not cause trouble. Same for the
> bundled extensions.

Yeah, purged, reinstalled, and default UO ext. didn't fix it. :(
--
"Dear friends, I urge you, as aliens and strangers in the world, to abstain from sinful desires, which war against your soul." --1 Peter 2:11. RIP, ext. Seagate 5 TB portable HDD (Model: SRD0NF1)? :( GM(aundy) & TGIGFE on a Holy wk. :)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
> Wow, old OS/2?!

Well, the latest beta of ArcaOS, OEM version of OS/2 updated to install
on modern hardware
Dave

Dave Yeo <dave.r.yeo@gmail.com> wrote:
> Ant wrote:
> > Wow, old OS/2?!

> Well, the latest beta of ArcaOS, OEM version of OS/2 updated to install
> on modern hardware

Oh neat. How long had it been around? I should try it one day!
--
"Dear friends, I urge you, as aliens and strangers in the world, to abstain from sinful desires, which war against your soul." --1 Peter 2:11. RIP, ext. Seagate 5 TB portable HDD (Model: SRD0NF1)? :( GM(aundy) & TGIGFE on a Holy wk. :)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
> Dave Yeo <dave.r.yeo@gmail.com> wrote:
>> Ant wrote:
>>> Wow, old OS/2?!
>> Well, the latest beta of ArcaOS, OEM version of OS/2 updated to install
>> on modern hardware
> Oh neat. How long had it been around? I should try it one day!

Coming up to 6 years. Unluckily it is not free, IBM wants money and so
do the developers.
https://www.arcanoae.com/
Anyways, off topic
Dave

Dave Yeo <dave.r.yeo@gmail.com> wrote:
> Ant wrote:
> > Dave Yeo <dave.r.yeo@gmail.com> wrote:
> >> Ant wrote:
> >>> Wow, old OS/2?!
> >> Well, the latest beta of ArcaOS, OEM version of OS/2 updated to install
> >> on modern hardware
> > Oh neat. How long had it been around? I should try it one day!

> Coming up to 6 years. Unluckily it is not free, IBM wants money and so
> do the developers.
> https://www.arcanoae.com/
> Anyways, off topic
> Dave

Yeah, I saw. Boo. I guess it is good for legacy support for those who still need it.
--
"Seek good, not evil, that you may live. Then the LORD God Almighty will be with you, just as you say he is." --Amos 5:14. TGIGF, but2 many tech issues on a Holy wk!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )