SeaMonkey 2.53.17.1 has been released !!!

[ElTxolo]

• SeaMonkey 2.53.17.1 has been released (September 20, 2023)
  
  
  
  
  
  
  
  
  
  
  
  
  
  • Official announcement and release notes:
  • https://www.seamonkey-project.org/news#2023-09-20
  • https://www.seamonkey-project.org/relea ... 2.53.17.1/
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  Cheers!

[ElTxolo]

I would like to remind you, that in this version, several critical security issues have been fixed.

Therefore, it is recommended that all users upgrade to this latest version, SeaMonkey 2.53.17.1








Cheers !!

[Justinh]

10-4. Thanks for the heads up.

[raj_bhaskar]

Will this be available as an update (Help > Check for updates still says no update found), or will we have to download and install from the full installer on the website?

[ElTxolo]

10-4. Thanks for the heads up.

You're welcome !!

[ElTxolo]

Will this be available as an update (Help > Check for updates still says no update found), or will we have to download and install from the full installer on the website?

See:

• #seamonkey - seamonkey/20230920#c217681
  
  
  

  
  Website has now been updated (might need a release). If updates are not yet enable ewong will do later I am sure:
  https://www.seamonkey-project.org/relea ... 2.53.17.1/
  
  A second libwep fix for the upcoming Firefox esr115.3 is also already included.
  

  
  
  
  
  
  
  
  
  Cheers !!

[therube]

.

[Frank Lion]

An unexpected bonus of SeaMonkey 2.53.17.1 is that its memory usage seems to be about half of SeaMonkey 2.53.17 and earlier versions.

Earlier, I was researching something and was viewing one YT vid after another and I guarantee even a week ago that would produce high memory use, leading to slow/non responsiveness if allowed to build up too much. Not a problem for me, as I have a Windows program that changed colour with high memory use and I just use my SM restart button to restart about twice a day.

Today, with SeaMonkey 2.53.17.1 that excessive memory build-up is just not happening.

[frg]

Well compared to 2.53.17 it has a whooping 11 patches applied and most of them are for libwebp:

https://gitlab.com/seamonkey-project/se ... type=heads

I also picked the latest VS2019 compiler revision but that is it so a bit puzzled. Maybe google uses webp for yt images and the update is better now with this.

2.53.18 already has stuff like https://bugzilla.mozilla.org/show_bug.cgi?id=523950 in so I would understand if this one behaves better but 2.53.17.1 is basically a security only update for webp.

FRG

[Frank Lion]

... so I would understand if this one behaves better but 2.53.17.1 is basically a security only update for webp.

Yep, I saw that in the Release Notes.

It seemed unlikely to me, but I wasn't looking for this, it found me and it really is a thing and this was on a good range of tabs, as well -

Maybe google uses webp for yt images and the update is better now with this.

Page Info shows that YT is still using .jpg for its thumbnails, so it's not that. To be clear though it's not just YT, browsing any traditionally memory heavy sites and convential sites just doesn't seem to impact RAM as it did.

Will be interesting to see what other people report. Be good if it is as it seems though.

[CapnVideo]

I've had the update for a while now and it seems to crash a lot, then it will not restore from where it crashed even though the tabs appear in the restore box.
It's getting a bit irritating.

I'd still like LinkedIn to work on Seamonkey.
Now this machine has Seamonkey (default browser) Firefox, (preferred for business), and chrome (necessary for a few sites that do not display correctly on Firefox).
Truth is I have a dozen tabs open automatically on Chrome, probably 25 open on Firefoz at any given time, and Seamonkey just can't handle 10 any more.

[RDaneel]

... "Seamonkey just can't handle 10 any more"...

Hmm, I regularly use 165 tabs on my nightly Builds by Bill(tm) - on Win 11 Pro.

[OldBrowserInUse]

I'm finding issues, RequestPolicyContinued is no longer compatible. After trying several other versions to narrow down the problem, it started with 2.53.17 (meaning 2.53.16 was still compatible). This is almost as bad as losing NoScript, and a dealbreaker for me. I'll have to stay with 2.53.16 until this gets sorted.

I noticed in the beta thread that some people were finding extensions that broke, but I don't know how to apply the fixes they found, or if they are even relevant for RequestPolicyContinued.

At the same time these versions both no longer show tooltips with the full timestamps when mouse-hovering over a date in github issues threads, this also used to work in 2.53.14, but not in 2.53.16.

The same old list of broken websites continues - any Discourse based forums, can't login to Comcast, some banking sites, etc. Oddly several grocery stores are added recently, though this looks more like site updates (which now require a chrome based browser) rather than anything about the seamonkey version (ie, the old versions no longer work there either).