On 05/08/2017 10:17, BERTRAND Joël wrote:
>       Hello,
> 
>       I use seamonkey for a long time and on one of my workstations, it often 
> crashes since 2.40 if I remember) with following trace in terminal :
> 
> ATTENTION: default value of option force_s3tc_enable overridden by 
> environment.
> 1501866871483   addons.update-checker   WARN    Update manifest for 
> mod...@themes.mozilla.org did not contain an updates property
> 1501866871509   addons.update-checker   WARN    Update manifest for 
> {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
> 1501866871517   addons.update-checker   WARN    Update manifest for 
> langpack...@seamonkey.mozilla.org did not contain an updates property
> [aac @ 0x7f38320ab000] illegal icc
> Assertion failure: !mDoingStableStates, at 
> /builds/slave/rel-c-rel-lnx64-bld/build/mozilla/xpcom/base/CycleCollectedJSRuntime.cpp:1312
> #01: ???[/opt/seamonkey/libxul.so +0x1173eec]
> #02: ???[/opt/seamonkey/libxul.so +0xcbfa2d]
> #03: NS_InvokeByIndex[/opt/seamonkey/libxul.so +0xcc69fb]
> #04: ???[/opt/seamonkey/libxul.so +0x117fca3]
> #05: ???[/opt/seamonkey/libxul.so +0x11875fb]
> #06: ???[/opt/seamonkey/libxul.so +0x2d4bd0b]
> #07: ???[/opt/seamonkey/libxul.so +0x2d3e2e7]
> #08: ???[/opt/seamonkey/libxul.so +0x2d4ba4d]
> #09: ???[/opt/seamonkey/libxul.so +0x2d4bc69]
> #10: ???[/opt/seamonkey/libxul.so +0x2fc5d75]
> #11: ??? (???:???)
> ExceptionHandler::GenerateDump cloned child 20779
> ExceptionHandler::SendContinueSignalToChild sent continue signal to child
> ExceptionHandler::WaitForContinueSignal waiting for continue signal...
> 
>       This workstation runs Linux Debian testing (amd64). I have other debian 
> system in the same configuration that don't trigger the same issue.
> 
>       I have tested binaries from mozilla ftp, binaries from ubuntu and I 
> have tried to build seamonkey from sources. I always obtain the same bug.
> 
>       All idea to fix this issue will be welcome.

Type about:crashes in the URL bar.
Copy/paste the contents here.

Note that 2.48 has been released. It might be worth
upgrading to that version.

And Adrian Kalla has even released unofficial 2.49.1
builds, which may have fixed the issue (or not).

@FRG: are Adrian's builds available somewhere else?

Regards.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to