Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.seamonkey > #8119

Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22

Show all headers | View raw

Barryedwin1 wrote:
> frg wrote on 8/11/25 8:07 pm:
>>
>> Michael Lueck wrote:
>>> Greetings Barry,
>> ...
>>
>> I have an ubuntu 22.4 LTS vm left which I now and then use for tests. Use 
>> Rocky Linux 8 vm for building and OpenSuse Leap 1.56 (16 bahhh) as a backup 
>> server. I updated the vm to the latest level and unpacked the official 
>> package into the 22.4 opt/seamonkey directory using a root account and ran 
>> it under my normal user. I was unable to confim the exit crash in any way.
>>
>> Is the crash listed under about:crashes? If yes can you post the crash id.
> 
> Currently on :-
> U-24-04.3 X11 SeaMonkey 2.53.23 beta 1 pre -20251104212101
> 
> Tell the truth, I mostly have the crash reporter pane disabled (all boxes 
> unchecked), but the last one listed under the heading:
> "Submitted Crash Reports"
> Report ID     Date Submitted
> 123491     5/11/25, 8:18 pm
> <https://app.bugsplat.com/v2/crash?database=seamonkey_project&id=123491>
> 
> Opening an account there says this is an unknown crash report - ergo it is 
> blank ..
> 
> Did I mention that for me, it is an erratic bug!

This is a null pointer crash. You are running openWith. I know this one can 
cause a recursive loop problem and a crash if you try it on the wrong link 
type. Forgot which one but I think mailto or another non standard scheme. 
There are a few other old ones but can't say if they are still safe. Element 
Hiding Helper might need an update.

To make matters worse we broke BugSplat reporting. Version number is bad in 
the crashes. I didn't have time to even look at BugSplat lately and only do it 
when something is reported so never saw it. Doh. Suspect a fast 2.53.23 is 
needed soon :) Doh

>> Over time would be wise to a distribution which still supports the x11 
>> layer. Not enough devs around to make Wayland support happen in the near 
>> future. We are not alone with this but not something I like.
>>
> Wise words indeed! Yes, I'll need to do this. I live inside SM Composer!

Worst case if we go out of business you can tuck it into a vm. But don't plan to.

> I'm feeling it may be a system timeout on SM, as my profile is:-
> 16,260 items, totalling 5.2 GB,
> albeit my system is:-
> ASUS Pro WS X570-ACE AMD Ryzen™ 9 3900X × 24 32.0-GiB-DDR4 2.5TB NVMe
> so the hardware shouldn't bottleneck it.
> 

Do a bookmarks integrity check and maybe nuke Offline Website Data and cookies 
one time. I have set to do these two every time I close SM but some might 
prefer not to do.

> Can't argue with that! You are not exactly an island in those sentiments. 
> Comprehensive computing seems to make way for specialisation. Smartphones are 
> commodities that like the gap between rich and poor, the gap between power 
> computerisation and commodity computing becomes even wider with time. 
> Proprietorialism and security also now seem to be identical. Ownership can't 
> value public freedom.

/rant on
In the 90ies and start of 2000 it was fun and I updated constantly. I love 
testing new stuff but the new stuff became dull over time. Now its just ui 
dumbing down and putting more freedom to configure things into a box and lock 
it. Every website redesign I have seen in the last years was bad when it comes 
usability on the desktop. 90pt font sizes, no content, endless drivel about 
how eco friendly even the most eco unfriendly company is instead of real news 
and so on. AI is the next level. We search for you and you just need to 
believe us. Takes away basic skills over time. I really thing AI can help like 
in testing stuff or checking results for anomalies among lots of other things 
but it is not intelligence and won't be for a long time if ever.

> 
> I surely do hope a Linux-distro does optimise for X11, but I guess progress 
> has to be accommodated too. We just need to find solutions.

Whatever progress means this day.

/rant off


> Thanks for all you've done for SM and myself as a user, seems entirely 
> inadequate. We don't say it enough, but you and your fellow devs efforts are 
> genuinely valued and appreciated by we users. Much appreciated. Barry.

I am selfish and SeaMonkey is my browser for almost 30 years now since 
Netscape 2 on OS/2. So doing code work. On the sites it still works it is 
still the most usable and best. Only Vivaldi comes somewhat close but lacks 
some stuff.

FRG

Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-04 10:07 -0500
  Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-04 16:23 +0100
    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-04 11:59 -0500
      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Daniel70 <daniel47@nomail.afraid.org> - 2025-11-05 19:56 +1100
      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-11-05 16:30 +0100
        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-05 11:48 -0500
  Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-05 20:32 +0800
  Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-05 23:08 +0800
    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-05 12:06 -0500
      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-08 13:07 +0100
        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-09 01:27 +0800
          Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-08 19:44 +0100
            Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-08 16:26 -0500
              Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-17 12:04 +0100
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-11-17 14:38 +0100
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-17 17:03 +0100
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 "Paul B. Gallagher" <mozilla@pbg-translations.com> - 2025-11-17 11:10 -0500
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-17 18:00 +0100
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Daniel70 <daniel47@nomail.afraid.org> - 2025-11-18 20:37 +1100
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-18 23:30 +0800
            Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-09 10:09 +0800
      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-08 12:07 -0500

csiph-web