Open Bug 2027057 Opened 7 months ago Updated 3 months ago

crashes and freezes in macos 26.4

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Version:
SeaMonkey 2.53
Type:
defect

Tracking

(Not tracked)

People

(Reporter: long, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:149.0) Gecko/20100101 Firefox/149.0

Steps to reproduce:

Nothing specific. Leave Seamonkey running in Background. Click a link in an email. Seems random. This all started after upgrading to MacOS 26.4. Previous versions of 26 worked fine. Running in safe mode does not help. SM 2.53.23

Actual results:

Seamonkey either crashes (asking me to report it to seamonkey) or freezes (where I have to Force Quit the app and report it to Apple)

Expected results:

No crashes or freezes

I've submitted quite a few crash reports for this.

142547 3/30/26, 2:26 PM
View
142546 3/30/26, 2:06 PM
View
142545 3/30/26, 1:58 PM
View
142536 3/30/26, 11:55 AM
View
142535 3/30/26, 11:46 AM
View
142133 3/27/26, 2:16 PM
View
142132 3/27/26, 2:14 PM
View
142131 3/27/26, 2:01 PM
View
142122 3/27/26, 12:34 PM
View
142121 3/27/26, 12:32 PM
View
142118 3/27/26, 12:12 PM
View
142081 3/27/26, 12:05 PM
View
142071 3/27/26, 8:31 AM

I will see if I find some time to look at them over easter.

Probably notning we can do but wait for a fix. Apple code quality is not was it once was.

The crash reports are unfortunately empty. Wonder if it has something to do with Rosetta 2. Apple plans to discontinue this. We put more stuff in to be able to do native builds but not there yet. Notarization is another hurdle.

Bummer, well let me know if you need any additional troubleshooting from this side, I've been known to be a pretty determined debugger.

I sometimes see messages like this in my terminal window:

out of memory: 0x0000000000000048 bytes requested

When you mentioned "waiting for a fix" did you mean a MacOS update?

When you mentioned "waiting for a fix" did you mean a MacOS update?

Yes. Seems other programs now also crash regularly with 26.4 and Mozilla also needed to put a workaround in Firefox for base 26 (does not apply to our code). Nontheless we need to fix our crash reporter and see where the real problem lies but not enough people around to do it fast. Sorry.

Status: UNCONFIRMED → NEW
Ever confirmed: true

seems like 26.5 has not fixed the problem

still broken with 26.6

You need to log in before you can comment on or make changes to this bug.