Re: 2.46 crash

2017-08-06 Thread BERTRAND Joël

Frank-Rainer Grahl a écrit :

Bug is marked fixed for (unreleased) 2.47. Might be fixed in 2.48:


OK. I'm trying.

Regards,

JKB

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


Re: 2.46 crash

2017-08-05 Thread Frank-Rainer Grahl

Bug is marked fixed for (unreleased) 2.47. Might be fixed in 2.48:

https://bugzilla.mozilla.org/show_bug.cgi?id=1276853

Please try this one.

FRG

BERTRAND Joël wrote:

Mason83 a écrit :

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.






 Best regards,

 JKB

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


Re: 2.46 crash

2017-08-05 Thread BERTRAND Joël

Mason83 a écrit :

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   WARNUpdate manifest for
mod...@themes.mozilla.org did not contain an updates property
1501866871509   addons.update-checker   WARNUpdate manifest for
{972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
1501866871517   addons.update-checker   WARNUpdate 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.


Date d’envoi
bp-b9c22269-2bb5-4878-a3e0-71cb10170609
09/06/2017  09:39
bp-1e57d532-c83d-4a28-a94c-fd50e0170601
01/06/2017  19:52
bp-ccebf685-3be7-4558-87a4-c26b10170511
11/05/2017  09:17
bp-288846a5-a762-4f15-b7e7-134960170428
28/04/2017  08:41
bp-f360fd77-e1e2-4588-876f-30d0b0170426
26/04/2017  08:55
bp-75fdefcc-e6ad-44f7-bd9f-5d6a80170423
23/04/2017  09:27
bp-787bd654-ae8f-4fe4-b346-e4ff80170422
22/04/2017  09:33
bp-85223044-0ed6-41a8-909e-ced410170420
20/04/2017  19:07
bp-d1260818-4f3b-4de8-bda0-1df062170411
11/04/2017  08:37
bp-7765e564-3f73-4bb4-b916-17a3b2170407
07/04/2017  09:02
bp-ad074933-9826-4f1d-9c4e-695a52170406
06/04/2017  08:41
bp-093f6b20-2193-4396-a10e-080752170404
04/04/2017  20:33
bp-deee479c-2aba-4fa3-a54a-70ec92170330
30/03/2017  09:16
bp-3a2d8aad-76a4-4fc5-8b5e-f85dc2170328
28/03/2017  09:36
bp-49dd6055-5ba8-4a02-9f2d-2a30b2170323
23/03/2017  22:27
bp-762af956-5116-4b77-be9c-cbd1b2170321
21/03/2017  20:29
bp-4662eafb-4058-4041-b01c-e20d62170320
20/03/2017  08:54
bp-19c7a63f-b36d-4a6e-b29f-fcea82170315
15/03/2017  20:34
bp-f79850f8-c4ee-40d3-8180-489df2170314
14/03/2017  23:46
bp-ad1698e5-ccd5-4810-a25d-7e2772160229
29/02/2016  19:44
bp-d31da402-0790-4b70-b2ec-121d92151123
23/11/2015  23:24
bp-e6242a0b-d45e-42ff-ac84-6ffc72151123
23/11/2015  23:24
bp-798197ad-a178-410a-ac2c-5662e2150412
12/04/2015  13:00
bp-ee0c52c4-b5e0-4c19-b30b-ee4c22150125
25/01/2015  23:00
bp-91dc232f-150c-404b-8f0e-2f06c2141204
04/12/2014  23:47
bp-1ef77fae-ba56-4548-8ace-fee312141113
13/11/2014  22:51
bp-7c48c408-798c-4971-8559-507f62141019
20/10/2014  00:20

Best regards,

JKB
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.46 crash

2017-08-05 Thread Mason83
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   WARNUpdate manifest for 
> mod...@themes.mozilla.org did not contain an updates property
> 1501866871509   addons.update-checker   WARNUpdate manifest for 
> {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
> 1501866871517   addons.update-checker   WARNUpdate 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


2.46 crash

2017-08-05 Thread BERTRAND Joël

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   WARNUpdate manifest for 
mod...@themes.mozilla.org did not contain an updates property
1501866871509   addons.update-checker   WARNUpdate manifest for 
{972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
1501866871517   addons.update-checker   WARNUpdate 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.

Best regards,

JKB
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey