Crashes #4

SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do 
need to update the program finally...I've been hesitant to do it since I 
have had no problems with SM until today.  Anyway, W-10, SM 2.49.1 
(yeah, I know, very out of date).

Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still, 
I'm always afraid to update SeaMonkey - afraid that my profile will get 
corrupted or something will go wrong.  I'm just curious if experts think 
that upgrading to 2.49.4 (which seems to be the latest version) would 
stop these annoying crashes.

-- 
Ken Rudolph
0
Ken
12/31/2018 6:16:45 AM
mozilla.support.seamonkey 13072 articles. 0 followers. Post Follow

30 Replies
47 Views

Similar Articles

[PageSpeed] 49

Without a crash id it is impossible to tell. Known problems with Win 10 where 
fixed in later 2.49 versions but if the crashes just started probably Win 10 
is the problem.

2.49.4 should not crash and burn and you will be able to go back. But as 
always a recent profile backup is advised.

FRG

Ken Rudolph wrote:
> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do need to 
> update the program finally...I've been hesitant to do it since I have had no 
> problems with SM until today.  Anyway, W-10, SM 2.49.1 (yeah, I know, very out 
> of date).
> 
> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still, I'm 
> always afraid to update SeaMonkey - afraid that my profile will get corrupted 
> or something will go wrong.  I'm just curious if experts think that upgrading 
> to 2.49.4 (which seems to be the latest version) would stop these annoying 
> crashes.
> 
0
Frank
12/31/2018 11:14:57 AM
Ken Rudolph wrote on 31/12/2018 5:16 PM:
> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do 
> need to update the program finally...I've been hesitant to do it since I 
> have had no problems with SM until today.  Anyway, W-10, SM 2.49.1 
> (yeah, I know, very out of date).
> 
> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still, 
> I'm always afraid to update SeaMonkey - afraid that my profile will get 
> corrupted or something will go wrong.  I'm just curious if experts think 
> that upgrading to 2.49.4 (which seems to be the latest version) would 
> stop these annoying crashes.
> 
Ken, is there anything interesting showing in the Error Console 
(Tools->Web Development->Error Console)??

Might be worthwhile clearing the Error Console first and then checking 
it out again after you experience problems.

(I only go as far back as Netscape Navigator Ver 0.9 ! ;-P )

-- 
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171015235623
0
Daniel
12/31/2018 12:30:58 PM
Ken Rudolph wrote:
> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do 
> need to update the program finally...I've been hesitant to do it since I 
> have had no problems with SM until today.  Anyway, W-10, SM 2.49.1 
> (yeah, I know, very out of date).
> 
> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still, 
> I'm always afraid to update SeaMonkey - afraid that my profile will get 
> corrupted or something will go wrong.  I'm just curious if experts think 
> that upgrading to 2.49.4 (which seems to be the latest version) would 
> stop these annoying crashes.
> 

Do you have any add-ons which have been updated recently?
Does about:crashes show anything useful?  (it never has for me though)
Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
2.49.1 counts as "recent" in my book, it should be stable but something 
is causing it to die.
0
A
12/31/2018 12:40:21 PM
A Williams wrote:
> Ken Rudolph wrote:
>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>> need to update the program finally...I've been hesitant to do it since
>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>> (yeah, I know, very out of date).
>>
>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still,
>> I'm always afraid to update SeaMonkey - afraid that my profile will
>> get corrupted or something will go wrong.  I'm just curious if experts
>> think that upgrading to 2.49.4 (which seems to be the latest version)
>> would stop these annoying crashes.
>>
> 
> Do you have any add-ons which have been updated recently?
> Does about:crashes show anything useful?  (it never has for me though)
> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
> 2.49.1 counts as "recent" in my book, it should be stable but something
> is causing it to die.

I don't know what is going on, but I have had three crashes in the last
few days.  Per about:crashes

Report ID 	Date Submitted
bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
	12/31/18	5:52 AM
bp-05ab3548-b184-4461-a69d-423500181225
	12/24/18	7:45 PM
bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
	12/20/18	3:00 PM

Prior to this my last crash was in June.  I have no idea how to read
these and determine the cause.

Dave
0
David
12/31/2018 1:29:22 PM
Hi,

David H. Durgee a écrit le 31/12/2018 à 14:29 :
> A Williams wrote:
>> Ken Rudolph wrote:
>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>>> need to update the program finally...I've been hesitant to do it since
>>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>>> (yeah, I know, very out of date).
>>>
>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still,
>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>> get corrupted or something will go wrong.  I'm just curious if experts
>>> think that upgrading to 2.49.4 (which seems to be the latest version)
>>> would stop these annoying crashes.
>>>
>>
>> Do you have any add-ons which have been updated recently?
>> Does about:crashes show anything useful?  (it never has for me though)
>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>> 2.49.1 counts as "recent" in my book, it should be stable but something
>> is causing it to die.
> 
> I don't know what is going on, but I have had three crashes in the last
> few days.  Per about:crashes
> 
> Report ID 	Date Submitted
> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
> 	12/31/18	5:52 AM
> bp-05ab3548-b184-4461-a69d-423500181225
> 	12/24/18	7:45 PM
> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
> 	12/20/18	3:00 PM
> 
> Prior to this my last crash was in June.  I have no idea how to read
> these and determine the cause.
> 
> Dave
> 

I didn't found those reports, crash-stats.mozilla.com give me my crashes
and not your crashes...


I think you have to click on the links that you found after
about:crashes and publish the urls which will be like this one :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.



-- 

Sorry for possible mistakes in English!
http://pasdenom.info/
0
Yamo
12/31/2018 1:53:59 PM
https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231

This is Bug 1500759. Already fixed in 2.53. Need to see if it applies clean to 
2.49 and then it will be in 2.49.5.

FRG

Yamo' wrote:
> Hi,
> 
> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>> A Williams wrote:
>>> Ken Rudolph wrote:
>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>>>> need to update the program finally...I've been hesitant to do it since
>>>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>>>> (yeah, I know, very out of date).
>>>>
>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still,
>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>> get corrupted or something will go wrong.  I'm just curious if experts
>>>> think that upgrading to 2.49.4 (which seems to be the latest version)
>>>> would stop these annoying crashes.
>>>>
>>>
>>> Do you have any add-ons which have been updated recently?
>>> Does about:crashes show anything useful?  (it never has for me though)
>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>> 2.49.1 counts as "recent" in my book, it should be stable but something
>>> is causing it to die.
>>
>> I don't know what is going on, but I have had three crashes in the last
>> few days.  Per about:crashes
>>
>> Report ID 	Date Submitted
>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>> 	12/31/18	5:52 AM
>> bp-05ab3548-b184-4461-a69d-423500181225
>> 	12/24/18	7:45 PM
>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>> 	12/20/18	3:00 PM
>>
>> Prior to this my last crash was in June.  I have no idea how to read
>> these and determine the cause.
>>
>> Dave
>>
> 
> I didn't found those reports, crash-stats.mozilla.com give me my crashes
> and not your crashes...
> 
> 
> I think you have to click on the links that you found after
> about:crashes and publish the urls which will be like this one :
> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
> 
> 
> 
0
Frank
12/31/2018 2:43:15 PM
Thanks for letting me know, Frank-Rainer.  Are the other two the same
bug?  Is there anything to be done on my end until the fixed release is
available?

Dave


> Frank-Rainer Grahl wrote:
> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
> 
> 
> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
> clean to 2.49 and then it will be in 2.49.5.
> 
> FRG
> 
> Yamo' wrote:
>> Hi,
>>
>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>> A Williams wrote:
>>>> Ken Rudolph wrote:
>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>>>>> need to update the program finally...I've been hesitant to do it since
>>>>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>>>>> (yeah, I know, very out of date).
>>>>>
>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still,
>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>> get corrupted or something will go wrong.  I'm just curious if experts
>>>>> think that upgrading to 2.49.4 (which seems to be the latest version)
>>>>> would stop these annoying crashes.
>>>>>
>>>>
>>>> Do you have any add-ons which have been updated recently?
>>>> Does about:crashes show anything useful?  (it never has for me though)
>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>> 2.49.1 counts as "recent" in my book, it should be stable but something
>>>> is causing it to die.
>>>
>>> I don't know what is going on, but I have had three crashes in the last
>>> few days.  Per about:crashes
>>>
>>> Report ID     Date Submitted
>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>     12/31/18    5:52 AM
>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>     12/24/18    7:45 PM
>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>     12/20/18    3:00 PM
>>>
>>> Prior to this my last crash was in June.  I have no idea how to read
>>> these and determine the cause.
>>>
>>> Dave
>>>
>>
>> I didn't found those reports, crash-stats.mozilla.com give me my crashes
>> and not your crashes...
>>
>>
>> I think you have to click on the links that you found after
>> about:crashes and publish the urls which will be like this one :
>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>
>>
>>
>>

0
David
12/31/2018 2:57:02 PM
A Williams wrote:
> Ken Rudolph wrote:
>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do 
>> need to update the program finally...I've been hesitant to do it since 
>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1 
>> (yeah, I know, very out of date).
>>
>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still, 
>> I'm always afraid to update SeaMonkey - afraid that my profile will 
>> get corrupted or something will go wrong.  I'm just curious if experts 
>> think that upgrading to 2.49.4 (which seems to be the latest version) 
>> would stop these annoying crashes.
>>
> 
> Do you have any add-ons which have been updated recently?
> Does about:crashes show anything useful?  (it never has for me though)
> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
> 2.49.1 counts as "recent" in my book, it should be stable but something 
> is causing it to die.

Every one of the crashes says that the reason is:

  	EXCEPTION_ACCESS_VIOLATION_READ

-- 
Ken Rudolph

0
Ken
12/31/2018 3:09:15 PM
Seems to be crypto related. I don't have access to the underlying bug just the 
changeset and a duplicate bug:

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

If the change applies clean I will see that Bills builds pick it up tomorrow:

http://www.wg9s.com/comm-esr/

ewong is still on our infra. It will still be some time till an official 
release follows unfortunately.

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

While he is working on the infra I am doing backports to 2.49.5 and 2.53.

Have a nice trip into the new year
FRG

David H. Durgee wrote:
> Thanks for letting me know, Frank-Rainer.  Are the other two the same
> bug?  Is there anything to be done on my end until the fixed release is
> available?
> 
> Dave
> 
> 
>> Frank-Rainer Grahl wrote:
>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>
>>
>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>> clean to 2.49 and then it will be in 2.49.5.
>>
>> FRG
>>
>> Yamo' wrote:
>>> Hi,
>>>
>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>> A Williams wrote:
>>>>> Ken Rudolph wrote:
>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>>>>>> need to update the program finally...I've been hesitant to do it since
>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>>>>>> (yeah, I know, very out of date).
>>>>>>
>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still,
>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>> get corrupted or something will go wrong.  I'm just curious if experts
>>>>>> think that upgrading to 2.49.4 (which seems to be the latest version)
>>>>>> would stop these annoying crashes.
>>>>>>
>>>>>
>>>>> Do you have any add-ons which have been updated recently?
>>>>> Does about:crashes show anything useful?  (it never has for me though)
>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>> 2.49.1 counts as "recent" in my book, it should be stable but something
>>>>> is causing it to die.
>>>>
>>>> I don't know what is going on, but I have had three crashes in the last
>>>> few days.  Per about:crashes
>>>>
>>>> Report ID     Date Submitted
>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>      12/31/18    5:52 AM
>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>      12/24/18    7:45 PM
>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>      12/20/18    3:00 PM
>>>>
>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>> these and determine the cause.
>>>>
>>>> Dave
>>>>
>>>
>>> I didn't found those reports, crash-stats.mozilla.com give me my crashes
>>> and not your crashes...
>>>
>>>
>>> I think you have to click on the links that you found after
>>> about:crashes and publish the urls which will be like this one :
>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>
>>>
>>>
>>>
> 
0
Frank
12/31/2018 3:34:55 PM
Patch applied clean and is now in the patch repo Bills builds use. All the 
crashes from David where caused by this.

Ken,

unless I see a crash id for the first report can't tell if it fixes this one 
too. Please post a crash id from about:crashes

FRG


Frank-Rainer Grahl wrote:
> Seems to be crypto related. I don't have access to the underlying bug just the 
> changeset and a duplicate bug:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
> 
> If the change applies clean I will see that Bills builds pick it up tomorrow:
> 
> http://www.wg9s.com/comm-esr/
> 
> ewong is still on our infra. It will still be some time till an official 
> release follows unfortunately.
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
> 
> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
> 
> Have a nice trip into the new year
> FRG
> 
> David H. Durgee wrote:
>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>> bug?  Is there anything to be done on my end until the fixed release is
>> available?
>>
>> Dave
>>
>>
>>> Frank-Rainer Grahl wrote:
>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231 
>>>
>>>
>>>
>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>> clean to 2.49 and then it will be in 2.49.5.
>>>
>>> FRG
>>>
>>> Yamo' wrote:
>>>> Hi,
>>>>
>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>> A Williams wrote:
>>>>>> Ken Rudolph wrote:
>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>>>>>>> need to update the program finally...I've been hesitant to do it since
>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>>>>>>> (yeah, I know, very out of date).
>>>>>>>
>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still,
>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>> get corrupted or something will go wrong.  I'm just curious if experts
>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest version)
>>>>>>> would stop these annoying crashes.
>>>>>>>
>>>>>>
>>>>>> Do you have any add-ons which have been updated recently?
>>>>>> Does about:crashes show anything useful?  (it never has for me though)
>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but something
>>>>>> is causing it to die.
>>>>>
>>>>> I don't know what is going on, but I have had three crashes in the last
>>>>> few days.  Per about:crashes
>>>>>
>>>>> Report ID     Date Submitted
>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>      12/31/18    5:52 AM
>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>      12/24/18    7:45 PM
>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>      12/20/18    3:00 PM
>>>>>
>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>> these and determine the cause.
>>>>>
>>>>> Dave
>>>>>
>>>>
>>>> I didn't found those reports, crash-stats.mozilla.com give me my crashes
>>>> and not your crashes...
>>>>
>>>>
>>>> I think you have to click on the links that you found after
>>>> about:crashes and publish the urls which will be like this one :
>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 
>>>>
>>>>
>>>>
>>>>
>>>>
>>
0
Frank
12/31/2018 3:58:40 PM
Will installing Bill's build cause any conflicts with future official
releases?  Given I am encountering these crashes I will probably install
it provided it is supported on Linux Mint x64 18.3 by its requirements.

Dave


> Frank-Rainer Grahl wrote:
> Patch applied clean and is now in the patch repo Bills builds use. All
> the crashes from David where caused by this.
> 
> Ken,
> 
> unless I see a crash id for the first report can't tell if it fixes this
> one too. Please post a crash id from about:crashes
> 
> FRG
> 
> 
> Frank-Rainer Grahl wrote:
>> Seems to be crypto related. I don't have access to the underlying bug
>> just the changeset and a duplicate bug:
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>
>> If the change applies clean I will see that Bills builds pick it up
>> tomorrow:
>>
>> http://www.wg9s.com/comm-esr/
>>
>> ewong is still on our infra. It will still be some time till an
>> official release follows unfortunately.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>
>> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
>>
>> Have a nice trip into the new year
>> FRG
>>
>> David H. Durgee wrote:
>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>> bug?  Is there anything to be done on my end until the fixed release is
>>> available?
>>>
>>> Dave
>>>
>>>
>>>> Frank-Rainer Grahl wrote:
>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>
>>>>
>>>>
>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>
>>>> FRG
>>>>
>>>> Yamo' wrote:
>>>>> Hi,
>>>>>
>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>> A Williams wrote:
>>>>>>> Ken Rudolph wrote:
>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>> maybe I do
>>>>>>>> need to update the program finally...I've been hesitant to do it
>>>>>>>> since
>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>> 2.49.1
>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>
>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee. 
>>>>>>>> Still,
>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>> experts
>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>> version)
>>>>>>>> would stop these annoying crashes.
>>>>>>>>
>>>>>>>
>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>> though)
>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>> something
>>>>>>> is causing it to die.
>>>>>>
>>>>>> I don't know what is going on, but I have had three crashes in the
>>>>>> last
>>>>>> few days.  Per about:crashes
>>>>>>
>>>>>> Report ID     Date Submitted
>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>      12/31/18    5:52 AM
>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>      12/24/18    7:45 PM
>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>      12/20/18    3:00 PM
>>>>>>
>>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>>> these and determine the cause.
>>>>>>
>>>>>> Dave
>>>>>>
>>>>>
>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>> crashes
>>>>> and not your crashes...
>>>>>
>>>>>
>>>>> I think you have to click on the links that you found after
>>>>> about:crashes and publish the urls which will be like this one :
>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>

0
David
12/31/2018 5:03:05 PM
Frank-Rainer Grahl wrote:
> Patch applied clean and is now in the patch repo Bills builds use. All 
> the crashes from David where caused by this.
> 
> Ken,
> 
> unless I see a crash id for the first report can't tell if it fixes this 
> one too. Please post a crash id from about:crashes

The most recent one:
https://crash-stats.mozilla.com/report/index/9863b11f-5f30-4c13-a5b8-90b750181231

The most recent spate of crashes started on 12/23 after no activity in a 
long while:
https://crash-stats.mozilla.com/report/index/b88da439-7815-4c22-9778-fa1720181223

Thanks for making the effort!!

--Ken


> 
> FRG
> 
> 
> Frank-Rainer Grahl wrote:
>> Seems to be crypto related. I don't have access to the underlying bug 
>> just the changeset and a duplicate bug:
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>
>> If the change applies clean I will see that Bills builds pick it up 
>> tomorrow:
>>
>> http://www.wg9s.com/comm-esr/
>>
>> ewong is still on our infra. It will still be some time till an 
>> official release follows unfortunately.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>
>> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
>>
>> Have a nice trip into the new year
>> FRG
>>
>> David H. Durgee wrote:
>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>> bug?  Is there anything to be done on my end until the fixed release is
>>> available?
>>>
>>> Dave
>>>
>>>
>>>> Frank-Rainer Grahl wrote:
>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231 
>>>>
>>>>
>>>>
>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>
>>>> FRG
>>>>
>>>> Yamo' wrote:
>>>>> Hi,
>>>>>
>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>> A Williams wrote:
>>>>>>> Ken Rudolph wrote:
>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but 
>>>>>>>> maybe I do
>>>>>>>> need to update the program finally...I've been hesitant to do it 
>>>>>>>> since
>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM 
>>>>>>>> 2.49.1
>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>
>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  
>>>>>>>> Still,
>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>>> get corrupted or something will go wrong.  I'm just curious if 
>>>>>>>> experts
>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest 
>>>>>>>> version)
>>>>>>>> would stop these annoying crashes.
>>>>>>>>
>>>>>>>
>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>> Does about:crashes show anything useful?  (it never has for me 
>>>>>>> though)
>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but 
>>>>>>> something
>>>>>>> is causing it to die.
>>>>>>
>>>>>> I don't know what is going on, but I have had three crashes in the 
>>>>>> last
>>>>>> few days.  Per about:crashes
>>>>>>
>>>>>> Report ID     Date Submitted
>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>      12/31/18    5:52 AM
>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>      12/24/18    7:45 PM
>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>      12/20/18    3:00 PM
>>>>>>
>>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>>> these and determine the cause.
>>>>>>
>>>>>> Dave
>>>>>>
>>>>>
>>>>> I didn't found those reports, crash-stats.mozilla.com give me my 
>>>>> crashes
>>>>> and not your crashes...
>>>>>
>>>>>
>>>>> I think you have to click on the links that you found after
>>>>> about:crashes and publish the urls which will be like this one :
>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>

0
Ken
12/31/2018 6:16:00 PM
Windows 10 Intel graphics driver crash. If you don't have a laptop get a new 
AMD or Nvidia card. Even the cheapest dedicated current generation card from 
them is better than the Intel junk.

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

If you run 1809 try the latest DCH drivers:

https://downloadcenter.intel.com/download/28445/Intel-Graphics-Driver-for-Windows-10?product=88345

FRG

Ken Rudolph wrote:
> Frank-Rainer Grahl wrote:
>> Patch applied clean and is now in the patch repo Bills builds use. All the 
>> crashes from David where caused by this.
>>
>> Ken,
>>
>> unless I see a crash id for the first report can't tell if it fixes this one 
>> too. Please post a crash id from about:crashes
> 
> The most recent one:
> https://crash-stats.mozilla.com/report/index/9863b11f-5f30-4c13-a5b8-90b750181231
> 
> The most recent spate of crashes started on 12/23 after no activity in a long 
> while:
> https://crash-stats.mozilla.com/report/index/b88da439-7815-4c22-9778-fa1720181223
> 
> Thanks for making the effort!!
> 
> --Ken
> 
> 
>>
>> FRG
>>
>>
>> Frank-Rainer Grahl wrote:
>>> Seems to be crypto related. I don't have access to the underlying bug just 
>>> the changeset and a duplicate bug:
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>
>>> If the change applies clean I will see that Bills builds pick it up tomorrow:
>>>
>>> http://www.wg9s.com/comm-esr/
>>>
>>> ewong is still on our infra. It will still be some time till an official 
>>> release follows unfortunately.
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>
>>> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
>>>
>>> Have a nice trip into the new year
>>> FRG
>>>
>>> David H. Durgee wrote:
>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>>> bug?  Is there anything to be done on my end until the fixed release is
>>>> available?
>>>>
>>>> Dave
>>>>
>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231 
>>>>>
>>>>>
>>>>>
>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>
>>>>> FRG
>>>>>
>>>>> Yamo' wrote:
>>>>>> Hi,
>>>>>>
>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>> A Williams wrote:
>>>>>>>> Ken Rudolph wrote:
>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I do
>>>>>>>>> need to update the program finally...I've been hesitant to do it since
>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM 2.49.1
>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>
>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee. Still,
>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if experts
>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest version)
>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>> Does about:crashes show anything useful?  (it never has for me though)
>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but something
>>>>>>>> is causing it to die.
>>>>>>>
>>>>>>> I don't know what is going on, but I have had three crashes in the last
>>>>>>> few days.  Per about:crashes
>>>>>>>
>>>>>>> Report ID     Date Submitted
>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>      12/31/18    5:52 AM
>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>      12/24/18    7:45 PM
>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>      12/20/18    3:00 PM
>>>>>>>
>>>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>>>> these and determine the cause.
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>
>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my crashes
>>>>>> and not your crashes...
>>>>>>
>>>>>>
>>>>>> I think you have to click on the links that you found after
>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
> 
0
Frank
12/31/2018 6:54:36 PM
No it has a few work in progress and a few minor private fixes from me in but 
these are stable and would not affect the official version. Even downgrading 
is safe. Famous last words :)

FRG



David H. Durgee wrote:
> Will installing Bill's build cause any conflicts with future official
> releases?  Given I am encountering these crashes I will probably install
> it provided it is supported on Linux Mint x64 18.3 by its requirements.
> 
> Dave
> 
> 
>> Frank-Rainer Grahl wrote:
>> Patch applied clean and is now in the patch repo Bills builds use. All
>> the crashes from David where caused by this.
>>
>> Ken,
>>
>> unless I see a crash id for the first report can't tell if it fixes this
>> one too. Please post a crash id from about:crashes
>>
>> FRG
>>
>>
>> Frank-Rainer Grahl wrote:
>>> Seems to be crypto related. I don't have access to the underlying bug
>>> just the changeset and a duplicate bug:
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>
>>> If the change applies clean I will see that Bills builds pick it up
>>> tomorrow:
>>>
>>> http://www.wg9s.com/comm-esr/
>>>
>>> ewong is still on our infra. It will still be some time till an
>>> official release follows unfortunately.
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>
>>> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
>>>
>>> Have a nice trip into the new year
>>> FRG
>>>
>>> David H. Durgee wrote:
>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>>> bug?  Is there anything to be done on my end until the fixed release is
>>>> available?
>>>>
>>>> Dave
>>>>
>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>
>>>>>
>>>>>
>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>
>>>>> FRG
>>>>>
>>>>> Yamo' wrote:
>>>>>> Hi,
>>>>>>
>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>> A Williams wrote:
>>>>>>>> Ken Rudolph wrote:
>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>>> maybe I do
>>>>>>>>> need to update the program finally...I've been hesitant to do it
>>>>>>>>> since
>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>>> 2.49.1
>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>
>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.
>>>>>>>>> Still,
>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>>> experts
>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>>> version)
>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>>> though)
>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>>> something
>>>>>>>> is causing it to die.
>>>>>>>
>>>>>>> I don't know what is going on, but I have had three crashes in the
>>>>>>> last
>>>>>>> few days.  Per about:crashes
>>>>>>>
>>>>>>> Report ID     Date Submitted
>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>       12/31/18    5:52 AM
>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>       12/24/18    7:45 PM
>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>       12/20/18    3:00 PM
>>>>>>>
>>>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>>>> these and determine the cause.
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>
>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>>> crashes
>>>>>> and not your crashes...
>>>>>>
>>>>>>
>>>>>> I think you have to click on the links that you found after
>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
> 
0
Frank
12/31/2018 6:56:56 PM
Frank-Rainer Grahl wrote:
> Windows 10 Intel graphics driver crash. If you don't have a laptop get a 
> new AMD or Nvidia card. Even the cheapest dedicated current generation 
> card from them is better than the Intel junk.
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1479795
> 
> If you run 1809 try the latest DCH drivers:
> 
> https://downloadcenter.intel.com/download/28445/Intel-Graphics-Driver-for-Windows-10?product=88345 

I'm sorry, I'm not tech capable enough to understand this.  I am running 
on a laptop (Dell Inspiron 7559).  My display info shows an NVIDIA 
GeForce GTX 960M, with driver ver.  25.21.14.1634.  Also, Intel HD 
Graphics 530, driver ver. 23.20.16.4973.  Every diagnostic I can find 
says that there are no new drivers available for my system.

I fear that running some unknown Intel Graphics Driver for Windows 
program might not be a good idea. Would your download deal correctly 
with my Intel HD 530?   I'm certainly willing to accept your diagnosis 
that my crashes are related to my graphics card.  What do you suggest I 
do?  I've already decided that my next computer will have a much better 
graphics card because I'd like to run VR content.

TIA!!!

--Ken

> 
> 
> FRG
> 
> Ken Rudolph wrote:
>> Frank-Rainer Grahl wrote:
>>> Patch applied clean and is now in the patch repo Bills builds use. 
>>> All the crashes from David where caused by this.
>>>
>>> Ken,
>>>
>>> unless I see a crash id for the first report can't tell if it fixes 
>>> this one too. Please post a crash id from about:crashes
>>
>> The most recent one:
>> https://crash-stats.mozilla.com/report/index/9863b11f-5f30-4c13-a5b8-90b750181231 
>>
>>
>> The most recent spate of crashes started on 12/23 after no activity in 
>> a long while:
>> https://crash-stats.mozilla.com/report/index/b88da439-7815-4c22-9778-fa1720181223 
>>
>>
>> Thanks for making the effort!!
>>
>> --Ken
>>
>>
>>>
>>> FRG
>>>
>>>
>>> Frank-Rainer Grahl wrote:
>>>> Seems to be crypto related. I don't have access to the underlying 
>>>> bug just the changeset and a duplicate bug:
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>>
>>>> If the change applies clean I will see that Bills builds pick it up 
>>>> tomorrow:
>>>>
>>>> http://www.wg9s.com/comm-esr/
>>>>
>>>> ewong is still on our infra. It will still be some time till an 
>>>> official release follows unfortunately.
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>>
>>>> While he is working on the infra I am doing backports to 2.49.5 and 
>>>> 2.53.
>>>>
>>>> Have a nice trip into the new year
>>>> FRG
>>>>
>>>> David H. Durgee wrote:
>>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>>>> bug?  Is there anything to be done on my end until the fixed 
>>>>> release is
>>>>> available?
>>>>>
>>>>> Dave
>>>>>
>>>>>
>>>>>> Frank-Rainer Grahl wrote:
>>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231 
>>>>>>
>>>>>>
>>>>>>
>>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>>
>>>>>> FRG
>>>>>>
>>>>>> Yamo' wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>>> A Williams wrote:
>>>>>>>>> Ken Rudolph wrote:
>>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but 
>>>>>>>>>> maybe I do
>>>>>>>>>> need to update the program finally...I've been hesitant to do 
>>>>>>>>>> it since
>>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM 
>>>>>>>>>> 2.49.1
>>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>>
>>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee. 
>>>>>>>>>> Still,
>>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile 
>>>>>>>>>> will
>>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if 
>>>>>>>>>> experts
>>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest 
>>>>>>>>>> version)
>>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>>> Does about:crashes show anything useful?  (it never has for me 
>>>>>>>>> though)
>>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact 
>>>>>>>>> mail-folders.
>>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but 
>>>>>>>>> something
>>>>>>>>> is causing it to die.
>>>>>>>>
>>>>>>>> I don't know what is going on, but I have had three crashes in 
>>>>>>>> the last
>>>>>>>> few days.  Per about:crashes
>>>>>>>>
>>>>>>>> Report ID     Date Submitted
>>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>      12/31/18    5:52 AM
>>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>>      12/24/18    7:45 PM
>>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>>      12/20/18    3:00 PM
>>>>>>>>
>>>>>>>> Prior to this my last crash was in June.  I have no idea how to 
>>>>>>>> read
>>>>>>>> these and determine the cause.
>>>>>>>>
>>>>>>>> Dave
>>>>>>>>
>>>>>>>
>>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my 
>>>>>>> crashes
>>>>>>> and not your crashes...
>>>>>>>
>>>>>>>
>>>>>>> I think you have to click on the links that you found after
>>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>

0
Ken
12/31/2018 7:25:35 PM
Looking at the directory below I see that the 32 bit was built, but the
64 bit still shows the 19th.  Do you need to apply the patch separately
for the 64 bit build?

Dave


> Frank-Rainer Grahl wrote:
> Patch applied clean and is now in the patch repo Bills builds use. All
> the crashes from David where caused by this.
> 
> Ken,
> 
> unless I see a crash id for the first report can't tell if it fixes this
> one too. Please post a crash id from about:crashes
> 
> FRG
> 
> 
> Frank-Rainer Grahl wrote:
>> Seems to be crypto related. I don't have access to the underlying bug
>> just the changeset and a duplicate bug:
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>
>> If the change applies clean I will see that Bills builds pick it up
>> tomorrow:
>>
>> http://www.wg9s.com/comm-esr/
>>
>> ewong is still on our infra. It will still be some time till an
>> official release follows unfortunately.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>
>> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
>>
>> Have a nice trip into the new year
>> FRG
>>
>> David H. Durgee wrote:
>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>> bug?  Is there anything to be done on my end until the fixed release is
>>> available?
>>>
>>> Dave
>>>
>>>
>>>> Frank-Rainer Grahl wrote:
>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>
>>>>
>>>>
>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>
>>>> FRG
>>>>
>>>> Yamo' wrote:
>>>>> Hi,
>>>>>
>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>> A Williams wrote:
>>>>>>> Ken Rudolph wrote:
>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>> maybe I do
>>>>>>>> need to update the program finally...I've been hesitant to do it
>>>>>>>> since
>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>> 2.49.1
>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>
>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee. 
>>>>>>>> Still,
>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>> experts
>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>> version)
>>>>>>>> would stop these annoying crashes.
>>>>>>>>
>>>>>>>
>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>> though)
>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>> something
>>>>>>> is causing it to die.
>>>>>>
>>>>>> I don't know what is going on, but I have had three crashes in the
>>>>>> last
>>>>>> few days.  Per about:crashes
>>>>>>
>>>>>> Report ID     Date Submitted
>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>      12/31/18    5:52 AM
>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>      12/24/18    7:45 PM
>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>      12/20/18    3:00 PM
>>>>>>
>>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>>> these and determine the cause.
>>>>>>
>>>>>> Dave
>>>>>>
>>>>>
>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>> crashes
>>>>> and not your crashes...
>>>>>
>>>>>
>>>>> I think you have to click on the links that you found after
>>>>> about:crashes and publish the urls which will be like this one :
>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>

0
David
12/31/2018 8:31:33 PM
On 12/31/18 2:25 PM, Ken Rudolph wrote:
> Frank-Rainer Grahl wrote:
>> Windows 10 Intel graphics driver crash. If you don't have a laptop get 
>> a new AMD or Nvidia card. Even the cheapest dedicated current 
>> generation card from them is better than the Intel junk.
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1479795
>>
>> If you run 1809 try the latest DCH drivers:
>>
>> https://downloadcenter.intel.com/download/28445/Intel-Graphics-Driver-for-Windows-10?product=88345 
> 
> 
> I'm sorry, I'm not tech capable enough to understand this.  I am running 
> on a laptop (Dell Inspiron 7559).  My display info shows an NVIDIA 
> GeForce GTX 960M, with driver ver.  25.21.14.1634.  Also, Intel HD 
> Graphics 530, driver ver. 23.20.16.4973.  Every diagnostic I can find 
> says that there are no new drivers available for my system.
> 
> I fear that running some unknown Intel Graphics Driver for Windows 
> program might not be a good idea. Would your download deal correctly 
> with my Intel HD 530?   I'm certainly willing to accept your diagnosis 
> that my crashes are related to my graphics card.  What do you suggest I 
> do?  I've already decided that my next computer will have a much better 
> graphics card because I'd like to run VR content.
> 
> TIA!!!
> 
> --Ken

Just my observation of the crash report.

It shows that you are using the Intel HD 530 graphics card, not the 
NVIDIA GeForce GTX 960M.

I don't know how you would do it, but switching to the NVIDIA card for 
graphics may help.

-- 
OS: Linux Mint 19.1 - Cinnamon Desktop
https://www.thunderbird.net/en-US/get-involved/
Rex called Don lazy and dumb as a rock in a much nicer way.
0
WaltS48
12/31/2018 10:42:14 PM
WaltS48 wrote:
> On 12/31/18 2:25 PM, Ken Rudolph wrote:
>> Frank-Rainer Grahl wrote:
>>> Windows 10 Intel graphics driver crash. If you don't have a laptop 
>>> get a new AMD or Nvidia card. Even the cheapest dedicated current 
>>> generation card from them is better than the Intel junk.
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1479795
>>>
>>> If you run 1809 try the latest DCH drivers:
>>>
>>> https://downloadcenter.intel.com/download/28445/Intel-Graphics-Driver-for-Windows-10?product=88345 
>>
>>
>>
>> I'm sorry, I'm not tech capable enough to understand this.  I am 
>> running on a laptop (Dell Inspiron 7559).  My display info shows an 
>> NVIDIA GeForce GTX 960M, with driver ver.  25.21.14.1634.  Also, Intel 
>> HD Graphics 530, driver ver. 23.20.16.4973.  Every diagnostic I can 
>> find says that there are no new drivers available for my system.
>>
>> I fear that running some unknown Intel Graphics Driver for Windows 
>> program might not be a good idea. Would your download deal correctly 
>> with my Intel HD 530?   I'm certainly willing to accept your diagnosis 
>> that my crashes are related to my graphics card.  What do you suggest 
>> I do?  I've already decided that my next computer will have a much 
>> better graphics card because I'd like to run VR content.
>>
>> TIA!!!
>>
>> --Ken
> 
> Just my observation of the crash report.
> 
> It shows that you are using the Intel HD 530 graphics card, not the 
> NVIDIA GeForce GTX 960M.
> 
> I don't know how you would do it, but switching to the NVIDIA card for 
> graphics may help.

I could use the Device Manager to disable the Intel card. I know how to 
do that.  But I really am afraid to modify the system so radically.  I 
just don't know why when both devices are shown to be present and in 
good working order, how and why the system opts for one over the other. 
My lack of knowledge is embarrassing.

Bottom line, I'm afraid to modify the graphics; and it seems that my 
version of SeaMonkey isn't causing the crashes.  So at this point, I 
guess I'm living with the crashes.

--Ken
> 

0
Ken
12/31/2018 11:05:38 PM
David,

fix should be in the 01/01 build.

FRG

David H. Durgee wrote:
> Looking at the directory below I see that the 32 bit was built, but the
> 64 bit still shows the 19th.  Do you need to apply the patch separately
> for the 64 bit build?
> 
> Dave
> 
> 
>> Frank-Rainer Grahl wrote:
>> Patch applied clean and is now in the patch repo Bills builds use. All
>> the crashes from David where caused by this.
>>
>> Ken,
>>
>> unless I see a crash id for the first report can't tell if it fixes this
>> one too. Please post a crash id from about:crashes
>>
>> FRG
>>
>>
>> Frank-Rainer Grahl wrote:
>>> Seems to be crypto related. I don't have access to the underlying bug
>>> just the changeset and a duplicate bug:
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>
>>> If the change applies clean I will see that Bills builds pick it up
>>> tomorrow:
>>>
>>> http://www.wg9s.com/comm-esr/
>>>
>>> ewong is still on our infra. It will still be some time till an
>>> official release follows unfortunately.
>>>
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>
>>> While he is working on the infra I am doing backports to 2.49.5 and 2.53.
>>>
>>> Have a nice trip into the new year
>>> FRG
>>>
>>> David H. Durgee wrote:
>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>>> bug?  Is there anything to be done on my end until the fixed release is
>>>> available?
>>>>
>>>> Dave
>>>>
>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>
>>>>>
>>>>>
>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>
>>>>> FRG
>>>>>
>>>>> Yamo' wrote:
>>>>>> Hi,
>>>>>>
>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>> A Williams wrote:
>>>>>>>> Ken Rudolph wrote:
>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>>> maybe I do
>>>>>>>>> need to update the program finally...I've been hesitant to do it
>>>>>>>>> since
>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>>> 2.49.1
>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>
>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.
>>>>>>>>> Still,
>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile will
>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>>> experts
>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>>> version)
>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>>> though)
>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>>> something
>>>>>>>> is causing it to die.
>>>>>>>
>>>>>>> I don't know what is going on, but I have had three crashes in the
>>>>>>> last
>>>>>>> few days.  Per about:crashes
>>>>>>>
>>>>>>> Report ID     Date Submitted
>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>       12/31/18    5:52 AM
>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>       12/24/18    7:45 PM
>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>       12/20/18    3:00 PM
>>>>>>>
>>>>>>> Prior to this my last crash was in June.  I have no idea how to read
>>>>>>> these and determine the cause.
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>
>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>>> crashes
>>>>>> and not your crashes...
>>>>>>
>>>>>>
>>>>>> I think you have to click on the links that you found after
>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
> 
0
Frank
1/1/2019 3:10:07 PM
This setup with two cards is called Nvidia Optimus.

https://www.nvidia.com/object/optimus_technology.html

Allows you to switch between cards so that when you travel it is lighter on 
the battery. It seems SeaMonkey uses the HD530. You can set it to use the 
GTX960M using the Nvidia control panel. If you use the laptop only stationary 
you can usually also disable it in Bios. There should be "use discrete 
graphics" and "disable optimus" settings in the Bios.

FRG

Ken Rudolph wrote:
> WaltS48 wrote:
>> On 12/31/18 2:25 PM, Ken Rudolph wrote:
>>> Frank-Rainer Grahl wrote:
>>>> Windows 10 Intel graphics driver crash. If you don't have a laptop get a 
>>>> new AMD or Nvidia card. Even the cheapest dedicated current generation 
>>>> card from them is better than the Intel junk.
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1479795
>>>>
>>>> If you run 1809 try the latest DCH drivers:
>>>>
>>>> https://downloadcenter.intel.com/download/28445/Intel-Graphics-Driver-for-Windows-10?product=88345 
>>>
>>>
>>>
>>>
>>> I'm sorry, I'm not tech capable enough to understand this.  I am running on 
>>> a laptop (Dell Inspiron 7559).  My display info shows an NVIDIA GeForce GTX 
>>> 960M, with driver ver.  25.21.14.1634.  Also, Intel HD Graphics 530, driver 
>>> ver. 23.20.16.4973.  Every diagnostic I can find says that there are no new 
>>> drivers available for my system.
>>>
>>> I fear that running some unknown Intel Graphics Driver for Windows program 
>>> might not be a good idea. Would your download deal correctly with my Intel 
>>> HD 530?   I'm certainly willing to accept your diagnosis that my crashes 
>>> are related to my graphics card.  What do you suggest I do?  I've already 
>>> decided that my next computer will have a much better graphics card because 
>>> I'd like to run VR content.
>>>
>>> TIA!!!
>>>
>>> --Ken
>>
>> Just my observation of the crash report.
>>
>> It shows that you are using the Intel HD 530 graphics card, not the NVIDIA 
>> GeForce GTX 960M.
>>
>> I don't know how you would do it, but switching to the NVIDIA card for 
>> graphics may help.
> 
> I could use the Device Manager to disable the Intel card. I know how to do 
> that.  But I really am afraid to modify the system so radically.  I just don't 
> know why when both devices are shown to be present and in good working order, 
> how and why the system opts for one over the other. My lack of knowledge is 
> embarrassing.
> 
> Bottom line, I'm afraid to modify the graphics; and it seems that my version 
> of SeaMonkey isn't causing the crashes.  So at this point, I guess I'm living 
> with the crashes.
> 
> --Ken
>>
> 
0
Frank
1/1/2019 3:16:40 PM
Yes, I saw it there this morning.

Now I need to address the prerequisites problem.  I am running Linux
Mint x64 18.3 (Sylvia) which is based on Ubuntu xenial.  While my distro
has libc-2.23.so it has libstdc++.so.6.0.21 while Bill's builds require
it to be 6.0.23 at least.

It is unclear to me where I can get the required library.  A web search
appears to indicate it comes with gcc 7.1.0, but I have no idea which
repository has a xenial compatible release of this, assuming I am
correct in my understanding of this.

Can you, or anyone, point me to the repository and package I can get the
required library in?

Dave


> Frank-Rainer Grahl wrote:
> David,
> 
> fix should be in the 01/01 build.
> 
> FRG
> 
> David H. Durgee wrote:
>> Looking at the directory below I see that the 32 bit was built, but the
>> 64 bit still shows the 19th.  Do you need to apply the patch separately
>> for the 64 bit build?
>>
>> Dave
>>
>>
>>> Frank-Rainer Grahl wrote:
>>> Patch applied clean and is now in the patch repo Bills builds use. All
>>> the crashes from David where caused by this.
>>>
>>> Ken,
>>>
>>> unless I see a crash id for the first report can't tell if it fixes this
>>> one too. Please post a crash id from about:crashes
>>>
>>> FRG
>>>
>>>
>>> Frank-Rainer Grahl wrote:
>>>> Seems to be crypto related. I don't have access to the underlying bug
>>>> just the changeset and a duplicate bug:
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>>
>>>> If the change applies clean I will see that Bills builds pick it up
>>>> tomorrow:
>>>>
>>>> http://www.wg9s.com/comm-esr/
>>>>
>>>> ewong is still on our infra. It will still be some time till an
>>>> official release follows unfortunately.
>>>>
>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>>
>>>> While he is working on the infra I am doing backports to 2.49.5 and
>>>> 2.53.
>>>>
>>>> Have a nice trip into the new year
>>>> FRG
>>>>
>>>> David H. Durgee wrote:
>>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>>>> bug?  Is there anything to be done on my end until the fixed
>>>>> release is
>>>>> available?
>>>>>
>>>>> Dave
>>>>>
>>>>>
>>>>>> Frank-Rainer Grahl wrote:
>>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>>
>>>>>> FRG
>>>>>>
>>>>>> Yamo' wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>>> A Williams wrote:
>>>>>>>>> Ken Rudolph wrote:
>>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>>>> maybe I do
>>>>>>>>>> need to update the program finally...I've been hesitant to do it
>>>>>>>>>> since
>>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>>>> 2.49.1
>>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>>
>>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.
>>>>>>>>>> Still,
>>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile
>>>>>>>>>> will
>>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>>>> experts
>>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>>>> version)
>>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>>>> though)
>>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact
>>>>>>>>> mail-folders.
>>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>>>> something
>>>>>>>>> is causing it to die.
>>>>>>>>
>>>>>>>> I don't know what is going on, but I have had three crashes in the
>>>>>>>> last
>>>>>>>> few days.  Per about:crashes
>>>>>>>>
>>>>>>>> Report ID     Date Submitted
>>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>       12/31/18    5:52 AM
>>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>>       12/24/18    7:45 PM
>>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>>       12/20/18    3:00 PM
>>>>>>>>
>>>>>>>> Prior to this my last crash was in June.  I have no idea how to
>>>>>>>> read
>>>>>>>> these and determine the cause.
>>>>>>>>
>>>>>>>> Dave
>>>>>>>>
>>>>>>>
>>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>>>> crashes
>>>>>>> and not your crashes...
>>>>>>>
>>>>>>>
>>>>>>> I think you have to click on the links that you found after
>>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>

0
David
1/2/2019 1:21:05 AM
David,

If you don't find it send me an email and I will do a private build for you.

FRG


David H. Durgee wrote:
> Yes, I saw it there this morning.
> 
> Now I need to address the prerequisites problem.  I am running Linux
> Mint x64 18.3 (Sylvia) which is based on Ubuntu xenial.  While my distro
> has libc-2.23.so it has libstdc++.so.6.0.21 while Bill's builds require
> it to be 6.0.23 at least.
> 
> It is unclear to me where I can get the required library.  A web search
> appears to indicate it comes with gcc 7.1.0, but I have no idea which
> repository has a xenial compatible release of this, assuming I am
> correct in my understanding of this.
> 
> Can you, or anyone, point me to the repository and package I can get the
> required library in?
> 
> Dave
> 
> 
>> Frank-Rainer Grahl wrote:
>> David,
>>
>> fix should be in the 01/01 build.
>>
>> FRG
>>
>> David H. Durgee wrote:
>>> Looking at the directory below I see that the 32 bit was built, but the
>>> 64 bit still shows the 19th.  Do you need to apply the patch separately
>>> for the 64 bit build?
>>>
>>> Dave
>>>
>>>
>>>> Frank-Rainer Grahl wrote:
>>>> Patch applied clean and is now in the patch repo Bills builds use. All
>>>> the crashes from David where caused by this.
>>>>
>>>> Ken,
>>>>
>>>> unless I see a crash id for the first report can't tell if it fixes this
>>>> one too. Please post a crash id from about:crashes
>>>>
>>>> FRG
>>>>
>>>>
>>>> Frank-Rainer Grahl wrote:
>>>>> Seems to be crypto related. I don't have access to the underlying bug
>>>>> just the changeset and a duplicate bug:
>>>>>
>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>>>
>>>>> If the change applies clean I will see that Bills builds pick it up
>>>>> tomorrow:
>>>>>
>>>>> http://www.wg9s.com/comm-esr/
>>>>>
>>>>> ewong is still on our infra. It will still be some time till an
>>>>> official release follows unfortunately.
>>>>>
>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>>>
>>>>> While he is working on the infra I am doing backports to 2.49.5 and
>>>>> 2.53.
>>>>>
>>>>> Have a nice trip into the new year
>>>>> FRG
>>>>>
>>>>> David H. Durgee wrote:
>>>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the same
>>>>>> bug?  Is there anything to be done on my end until the fixed
>>>>>> release is
>>>>>> available?
>>>>>>
>>>>>> Dave
>>>>>>
>>>>>>
>>>>>>> Frank-Rainer Grahl wrote:
>>>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies
>>>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>>>
>>>>>>> FRG
>>>>>>>
>>>>>>> Yamo' wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>>>> A Williams wrote:
>>>>>>>>>> Ken Rudolph wrote:
>>>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>>>>> maybe I do
>>>>>>>>>>> need to update the program finally...I've been hesitant to do it
>>>>>>>>>>> since
>>>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>>>>> 2.49.1
>>>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>>>
>>>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.
>>>>>>>>>>> Still,
>>>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile
>>>>>>>>>>> will
>>>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>>>>> experts
>>>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>>>>> version)
>>>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>>>>> though)
>>>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact
>>>>>>>>>> mail-folders.
>>>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>>>>> something
>>>>>>>>>> is causing it to die.
>>>>>>>>>
>>>>>>>>> I don't know what is going on, but I have had three crashes in the
>>>>>>>>> last
>>>>>>>>> few days.  Per about:crashes
>>>>>>>>>
>>>>>>>>> Report ID     Date Submitted
>>>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>>        12/31/18    5:52 AM
>>>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>>>        12/24/18    7:45 PM
>>>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>>>        12/20/18    3:00 PM
>>>>>>>>>
>>>>>>>>> Prior to this my last crash was in June.  I have no idea how to
>>>>>>>>> read
>>>>>>>>> these and determine the cause.
>>>>>>>>>
>>>>>>>>> Dave
>>>>>>>>>
>>>>>>>>
>>>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>>>>> crashes
>>>>>>>> and not your crashes...
>>>>>>>>
>>>>>>>>
>>>>>>>> I think you have to click on the links that you found after
>>>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>
> 
0
Frank
1/2/2019 7:38:08 AM
Hi,

Frank-Rainer Grahl a écrit le 31/12/2018 à 15:43 :
> This is Bug 1500759. Already fixed in 2.53. Need to see if it applies clean to 
> 2.49 and then it will be in 2.49.5.

I've tested 2.53 * and I had no javascript on the web with this build.

* Get on <http://www.wg9s.com/comm-253/>

-- 

Sorry for possible mistakes in English!
http://pasdenom.info/
0
Yamo
1/6/2019 9:06:11 AM
On 12/31/2018 7:09 AM, Ken Rudolph wrote:
> A Williams wrote:
>> Ken Rudolph wrote:
>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but maybe I 
>>> do need to update the program finally...I've been hesitant to do it 
>>> since I have had no problems with SM until today.  Anyway, W-10, SM 
>>> 2.49.1 (yeah, I know, very out of date).
>>>
>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.  Still, 
>>> I'm always afraid to update SeaMonkey - afraid that my profile will 
>>> get corrupted or something will go wrong.  I'm just curious if 
>>> experts think that upgrading to 2.49.4 (which seems to be the latest 
>>> version) would stop these annoying crashes.
>>>
>>
>> Do you have any add-ons which have been updated recently?
>> Does about:crashes show anything useful?  (it never has for me though)
>> Other than that: I'd clear Cache, empty Trash, Compact mail-folders.
>> 2.49.1 counts as "recent" in my book, it should be stable but 
>> something is causing it to die.
> 
> Every one of the crashes says that the reason is:
> 
>       EXCEPTION_ACCESS_VIOLATION_READ

Can you please kindly share the details of these crashes?
-- 
"I'm not a worker ant. I'm like a queen. Or maybe a king. But you never 
hear of king ants." --Sean Bentley
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.
    /\___/\                     http://aqfl.net & http://antfarm.ma.cx /
   / /\ /\ \                                 http://antfarm.home.dhs.org
  | |o   o| |   Axe ANT from its address if shown & e-mailing privately.
     \ _ /       Please kindly use Ant nickname & URL/link if crediting.
      ( )
0
Ant
1/6/2019 5:39:45 PM
Just encountered my first crash since installing 2.49.5 here:

https://crash-stats.mozilla.com/report/index/20358c6b-825c-4a73-91a3-922810190118

Definitely not related to the previous crashes, but I have no idea what
caused it or what I can do to avoid it in the future.

Dave


> Frank-Rainer Grahl wrote: David,
> 
> If you don't find it send me an email and I will do a private build for
> you.
> 
> FRG
> 
> 
> David H. Durgee wrote:
>> Yes, I saw it there this morning.
>>
>> Now I need to address the prerequisites problem.  I am running Linux
>> Mint x64 18.3 (Sylvia) which is based on Ubuntu xenial.  While my distro
>> has libc-2.23.so it has libstdc++.so.6.0.21 while Bill's builds require
>> it to be 6.0.23 at least.
>>
>> It is unclear to me where I can get the required library.  A web search
>> appears to indicate it comes with gcc 7.1.0, but I have no idea which
>> repository has a xenial compatible release of this, assuming I am
>> correct in my understanding of this.
>>
>> Can you, or anyone, point me to the repository and package I can get the
>> required library in?
>>
>> Dave
>>
>>
>>> Frank-Rainer Grahl wrote:
>>> David,
>>>
>>> fix should be in the 01/01 build.
>>>
>>> FRG
>>>
>>> David H. Durgee wrote:
>>>> Looking at the directory below I see that the 32 bit was built, but the
>>>> 64 bit still shows the 19th.  Do you need to apply the patch separately
>>>> for the 64 bit build?
>>>>
>>>> Dave
>>>>
>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>> Patch applied clean and is now in the patch repo Bills builds use. All
>>>>> the crashes from David where caused by this.
>>>>>
>>>>> Ken,
>>>>>
>>>>> unless I see a crash id for the first report can't tell if it fixes
>>>>> this
>>>>> one too. Please post a crash id from about:crashes
>>>>>
>>>>> FRG
>>>>>
>>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>>> Seems to be crypto related. I don't have access to the underlying bug
>>>>>> just the changeset and a duplicate bug:
>>>>>>
>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>>>>
>>>>>> If the change applies clean I will see that Bills builds pick it up
>>>>>> tomorrow:
>>>>>>
>>>>>> http://www.wg9s.com/comm-esr/
>>>>>>
>>>>>> ewong is still on our infra. It will still be some time till an
>>>>>> official release follows unfortunately.
>>>>>>
>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>>>>
>>>>>> While he is working on the infra I am doing backports to 2.49.5 and
>>>>>> 2.53.
>>>>>>
>>>>>> Have a nice trip into the new year
>>>>>> FRG
>>>>>>
>>>>>> David H. Durgee wrote:
>>>>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the
>>>>>>> same
>>>>>>> bug?  Is there anything to be done on my end until the fixed
>>>>>>> release is
>>>>>>> available?
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>>
>>>>>>>> Frank-Rainer Grahl wrote:
>>>>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it
>>>>>>>> applies
>>>>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>>>>
>>>>>>>> FRG
>>>>>>>>
>>>>>>>> Yamo' wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>>>>> A Williams wrote:
>>>>>>>>>>> Ken Rudolph wrote:
>>>>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>>>>>> maybe I do
>>>>>>>>>>>> need to update the program finally...I've been hesitant to
>>>>>>>>>>>> do it
>>>>>>>>>>>> since
>>>>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>>>>>> 2.49.1
>>>>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>>>>
>>>>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.
>>>>>>>>>>>> Still,
>>>>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile
>>>>>>>>>>>> will
>>>>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>>>>>> experts
>>>>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>>>>>> version)
>>>>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>>>>>> though)
>>>>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact
>>>>>>>>>>> mail-folders.
>>>>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>>>>>> something
>>>>>>>>>>> is causing it to die.
>>>>>>>>>>
>>>>>>>>>> I don't know what is going on, but I have had three crashes in
>>>>>>>>>> the
>>>>>>>>>> last
>>>>>>>>>> few days.  Per about:crashes
>>>>>>>>>>
>>>>>>>>>> Report ID     Date Submitted
>>>>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>>>        12/31/18    5:52 AM
>>>>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>>>>        12/24/18    7:45 PM
>>>>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>>>>        12/20/18    3:00 PM
>>>>>>>>>>
>>>>>>>>>> Prior to this my last crash was in June.  I have no idea how to
>>>>>>>>>> read
>>>>>>>>>> these and determine the cause.
>>>>>>>>>>
>>>>>>>>>> Dave
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>>>>>> crashes
>>>>>>>>> and not your crashes...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think you have to click on the links that you found after
>>>>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>

0
David
1/18/2019 2:43:12 PM
Just had my second crash with 2.49.5 here:

http://crash-stats.mozilla.com/report/index/bp-2ec4f1b0-e335-4e9c-9227-1527d0190120

Once again this is nothing like the previous crashes.  Once again I have
no idea what caused it or how to avoid it in the future.

On a related topic, is the "Restart Seamonkey" button supposed to work
on linux x64?  It doesn't work here, I have to start Seamonkey fresh
after every crash.

Dave



> Frank-Rainer Grahl wrote: David,
> 
> If you don't find it send me an email and I will do a private build for
> you.
> 
> FRG
> 
> 
> David H. Durgee wrote:
>> Yes, I saw it there this morning.
>>
>> Now I need to address the prerequisites problem.  I am running Linux
>> Mint x64 18.3 (Sylvia) which is based on Ubuntu xenial.  While my distro
>> has libc-2.23.so it has libstdc++.so.6.0.21 while Bill's builds require
>> it to be 6.0.23 at least.
>>
>> It is unclear to me where I can get the required library.  A web search
>> appears to indicate it comes with gcc 7.1.0, but I have no idea which
>> repository has a xenial compatible release of this, assuming I am
>> correct in my understanding of this.
>>
>> Can you, or anyone, point me to the repository and package I can get the
>> required library in?
>>
>> Dave
>>
>>
>>> Frank-Rainer Grahl wrote:
>>> David,
>>>
>>> fix should be in the 01/01 build.
>>>
>>> FRG
>>>
>>> David H. Durgee wrote:
>>>> Looking at the directory below I see that the 32 bit was built, but the
>>>> 64 bit still shows the 19th.  Do you need to apply the patch separately
>>>> for the 64 bit build?
>>>>
>>>> Dave
>>>>
>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>> Patch applied clean and is now in the patch repo Bills builds use. All
>>>>> the crashes from David where caused by this.
>>>>>
>>>>> Ken,
>>>>>
>>>>> unless I see a crash id for the first report can't tell if it fixes
>>>>> this
>>>>> one too. Please post a crash id from about:crashes
>>>>>
>>>>> FRG
>>>>>
>>>>>
>>>>> Frank-Rainer Grahl wrote:
>>>>>> Seems to be crypto related. I don't have access to the underlying bug
>>>>>> just the changeset and a duplicate bug:
>>>>>>
>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1499020
>>>>>>
>>>>>> If the change applies clean I will see that Bills builds pick it up
>>>>>> tomorrow:
>>>>>>
>>>>>> http://www.wg9s.com/comm-esr/
>>>>>>
>>>>>> ewong is still on our infra. It will still be some time till an
>>>>>> official release follows unfortunately.
>>>>>>
>>>>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1512882
>>>>>>
>>>>>> While he is working on the infra I am doing backports to 2.49.5 and
>>>>>> 2.53.
>>>>>>
>>>>>> Have a nice trip into the new year
>>>>>> FRG
>>>>>>
>>>>>> David H. Durgee wrote:
>>>>>>> Thanks for letting me know, Frank-Rainer.  Are the other two the
>>>>>>> same
>>>>>>> bug?  Is there anything to be done on my end until the fixed
>>>>>>> release is
>>>>>>> available?
>>>>>>>
>>>>>>> Dave
>>>>>>>
>>>>>>>
>>>>>>>> Frank-Rainer Grahl wrote:
>>>>>>>> https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> This is Bug 1500759. Already fixed in 2.53. Need to see if it
>>>>>>>> applies
>>>>>>>> clean to 2.49 and then it will be in 2.49.5.
>>>>>>>>
>>>>>>>> FRG
>>>>>>>>
>>>>>>>> Yamo' wrote:
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> David H. Durgee a écrit le 31/12/2018 à 14:29 :
>>>>>>>>>> A Williams wrote:
>>>>>>>>>>> Ken Rudolph wrote:
>>>>>>>>>>>> SeaMonkey has crashed 3 times today.  I'm not sure why; but
>>>>>>>>>>>> maybe I do
>>>>>>>>>>>> need to update the program finally...I've been hesitant to
>>>>>>>>>>>> do it
>>>>>>>>>>>> since
>>>>>>>>>>>> I have had no problems with SM until today.  Anyway, W-10, SM
>>>>>>>>>>>> 2.49.1
>>>>>>>>>>>> (yeah, I know, very out of date).
>>>>>>>>>>>>
>>>>>>>>>>>> Look, I go back to Netscape 0.8, so I'm not exactly a newbee.
>>>>>>>>>>>> Still,
>>>>>>>>>>>> I'm always afraid to update SeaMonkey - afraid that my profile
>>>>>>>>>>>> will
>>>>>>>>>>>> get corrupted or something will go wrong.  I'm just curious if
>>>>>>>>>>>> experts
>>>>>>>>>>>> think that upgrading to 2.49.4 (which seems to be the latest
>>>>>>>>>>>> version)
>>>>>>>>>>>> would stop these annoying crashes.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Do you have any add-ons which have been updated recently?
>>>>>>>>>>> Does about:crashes show anything useful?  (it never has for me
>>>>>>>>>>> though)
>>>>>>>>>>> Other than that: I'd clear Cache, empty Trash, Compact
>>>>>>>>>>> mail-folders.
>>>>>>>>>>> 2.49.1 counts as "recent" in my book, it should be stable but
>>>>>>>>>>> something
>>>>>>>>>>> is causing it to die.
>>>>>>>>>>
>>>>>>>>>> I don't know what is going on, but I have had three crashes in
>>>>>>>>>> the
>>>>>>>>>> last
>>>>>>>>>> few days.  Per about:crashes
>>>>>>>>>>
>>>>>>>>>> Report ID     Date Submitted
>>>>>>>>>> bp-0048e3a0-7eb3-4ba1-89ec-36c510181231
>>>>>>>>>>        12/31/18    5:52 AM
>>>>>>>>>> bp-05ab3548-b184-4461-a69d-423500181225
>>>>>>>>>>        12/24/18    7:45 PM
>>>>>>>>>> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>>>>>>>>>>        12/20/18    3:00 PM
>>>>>>>>>>
>>>>>>>>>> Prior to this my last crash was in June.  I have no idea how to
>>>>>>>>>> read
>>>>>>>>>> these and determine the cause.
>>>>>>>>>>
>>>>>>>>>> Dave
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I didn't found those reports, crash-stats.mozilla.com give me my
>>>>>>>>> crashes
>>>>>>>>> and not your crashes...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think you have to click on the links that you found after
>>>>>>>>> about:crashes and publish the urls which will be like this one :
>>>>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>
>>

0
David
1/20/2019 5:16:25 PM
Hi,

David H. Durgee a écrit le 20/01/2019 à 18:16 :
> Just had my second crash with 2.49.5 here:
> 
> http://crash-stats.mozilla.com/report/index/bp-2ec4f1b0-e335-4e9c-9227-1527d0190120
> 
> Once again this is nothing like the previous crashes.  Once again I have
> no idea what caused it or how to avoid it in the future.
> 
> On a related topic, is the "Restart Seamonkey" button supposed to work
> on linux x64?  It doesn't work here, I have to start Seamonkey fresh
> after every crash.



Is one those bugs reports describing your crash?

<https://crash-stats.mozilla.com/report/index/2ec4f1b0-e335-4e9c-9227-1527d0190120#tab-bugzilla>

-- 

Sorry for possible mistakes in English!
http://pasdenom.info/
0
Yamo
1/20/2019 6:06:26 PM
Yamo' wrote:
> Hi,
> 
> David H. Durgee a écrit le 20/01/2019 à 18:16 :
>> Just had my second crash with 2.49.5 here:
>>
>> http://crash-stats.mozilla.com/report/index/bp-2ec4f1b0-e335-4e9c-9227-1527d0190120
>>
>> Once again this is nothing like the previous crashes.  Once again I have
>> no idea what caused it or how to avoid it in the future.
>>
>> On a related topic, is the "Restart Seamonkey" button supposed to work
>> on linux x64?  It doesn't work here, I have to start Seamonkey fresh
>> after every crash.
> 
> 
> 
> Is one those bugs reports describing your crash?
> 
> <https://crash-stats.mozilla.com/report/index/2ec4f1b0-e335-4e9c-9227-1527d0190120#tab-bugzilla>
> 

I don't know enough about reading the crash report to match it to any of
the bug reports.  I was just closing a SM tab when it occurred, but it
is certainly possible something was going on in another tab or in the
mail/news window when it happened.  I trust someone who can read the
report will be able to match it to one of them or open a new one if it
needs to be done.

Dave
0
David
1/20/2019 6:53:55 PM
First one was deep in Linux gtk3. Probably a bug there but if you can 
reproduce it I can check.

Second one is an out of memory bug. Unless you have a reproducable case 
probably non fixable.

Looking at your extensions I don't see uBlock nor NoScript. Without both 
prepare for the worst. Todays websites are a pile of javascript third party 
garbage to track and present ads to you. They will eat memory in no time and 
hit obscure bugs in the javascript backend.

FRG

David H. Durgee wrote:
> Yamo' wrote:
>> Hi,
>>
>> David H. Durgee a écrit le 20/01/2019 à 18:16 :
>>> Just had my second crash with 2.49.5 here:
>>>
>>> http://crash-stats.mozilla.com/report/index/bp-2ec4f1b0-e335-4e9c-9227-1527d0190120
>>>
>>> Once again this is nothing like the previous crashes.  Once again I have
>>> no idea what caused it or how to avoid it in the future.
>>>
>>> On a related topic, is the "Restart Seamonkey" button supposed to work
>>> on linux x64?  It doesn't work here, I have to start Seamonkey fresh
>>> after every crash.
>>
>>
>>
>> Is one those bugs reports describing your crash?
>>
>> <https://crash-stats.mozilla.com/report/index/2ec4f1b0-e335-4e9c-9227-1527d0190120#tab-bugzilla>
>>
> 
> I don't know enough about reading the crash report to match it to any of
> the bug reports.  I was just closing a SM tab when it occurred, but it
> is certainly possible something was going on in another tab or in the
> mail/news window when it happened.  I trust someone who can read the
> report will be able to match it to one of them or open a new one if it
> needs to be done.
> 
> Dave
> 
0
Frank
1/20/2019 7:50:49 PM
Have not seen any further crashes and unclear what action on my part
relates to the crashes, so unlikely to be recreated.

I take an old school approach to keeping down the crap:

http://winhelp2002.mvps.org/hosts.htm

Seems to cut down the advertising noise quite well.

Dave


> Frank-Rainer Grahl wrote: First one was deep in Linux gtk3. Probably a bug there but if you can
> reproduce it I can check.
> 
> Second one is an out of memory bug. Unless you have a reproducable case
> probably non fixable.
> 
> Looking at your extensions I don't see uBlock nor NoScript. Without both
> prepare for the worst. Todays websites are a pile of javascript third
> party garbage to track and present ads to you. They will eat memory in
> no time and hit obscure bugs in the javascript backend.
> 
> FRG
> 
> David H. Durgee wrote:
>> Yamo' wrote:
>>> Hi,
>>>
>>> David H. Durgee a écrit le 20/01/2019 à 18:16 :
>>>> Just had my second crash with 2.49.5 here:
>>>>
>>>> http://crash-stats.mozilla.com/report/index/bp-2ec4f1b0-e335-4e9c-9227-1527d0190120
>>>>
>>>>
>>>> Once again this is nothing like the previous crashes.  Once again I
>>>> have
>>>> no idea what caused it or how to avoid it in the future.
>>>>
>>>> On a related topic, is the "Restart Seamonkey" button supposed to work
>>>> on linux x64?  It doesn't work here, I have to start Seamonkey fresh
>>>> after every crash.
>>>
>>>
>>>
>>> Is one those bugs reports describing your crash?
>>>
>>> <https://crash-stats.mozilla.com/report/index/2ec4f1b0-e335-4e9c-9227-1527d0190120#tab-bugzilla>
>>>
>>>
>>
>> I don't know enough about reading the crash report to match it to any of
>> the bug reports.  I was just closing a SM tab when it occurred, but it
>> is certainly possible something was going on in another tab or in the
>> mail/news window when it happened.  I trust someone who can read the
>> report will be able to match it to one of them or open a new one if it
>> needs to be done.
>>
>> Dave
>>

0
David
1/23/2019 5:21:09 PM
Reply: