Re: Crashes

[David H. Durgee]

Just encountered my first crash in a while:

https://crash-stats.mozilla.com/report/index/6f3660a9-db39-45a2-8c32-026350190419

I hit a miss in a news post and clicked to button to remove expired
posts and BOOM!  When I restarted seamonkey I found I was at the same
point.  Foolishly I tried again and BOOM! again.  I simply closed out
the missing post after that.

On a related topic, is the "restart seamonkey" supposed to work on
linux?  If so, it doesn't here in any case.

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

Re: Crashes

[David H. Durgee]

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?
>>>
>>> 
>>>
>>>
>>
>> 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
>>

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

Re: Crashes

[Frank-Rainer Grahl]

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?





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


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

Re: Crashes

[David H. Durgee]

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?
> 
> 
> 

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
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[Yamo']

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?



-- 

Sorry for possible mistakes in English!
http://pasdenom.info/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[David H. Durgee]

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
>> 

Re: Crashes

[David H. Durgee]

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 

Re: Crashes

[Ant via support-seamonkey]

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.
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[Yamo']

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 

-- 

Sorry for possible mistakes in English!
http://pasdenom.info/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[Frank-Rainer Grahl]

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 :
.













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

Re: Crashes

[David H. Durgee]

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 :
>>> .
>>>
>>>
>>>
>>>
>>>
>>>
>
>>

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

Re: Crashes

[Frank-Rainer Grahl]

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





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

Re: Crashes

[Frank-Rainer Grahl]

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 :
.










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

Re: Crashes

[Ken Rudolph]

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




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

Re: Crashes

[WaltS48]

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.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[David H. Durgee]

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 :
> .
>
>
>
>
>
>>>

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

Re: Crashes

[Ken Rudolph]

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/185:52 AM
bp-05ab3548-b184-4461-a69d-423500181225
 12/24/187:45 PM
bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
 12/20/183: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 :
. 












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

Re: Crashes

[Frank-Rainer Grahl]

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 :
.










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

Re: Crashes

[Frank-Rainer Grahl]

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 :
. 











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

Re: Crashes

[Ken Rudolph]

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/185:52 AM
bp-05ab3548-b184-4461-a69d-423500181225
 12/24/187:45 PM
bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
 12/20/183: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 :
. 










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

Re: Crashes

[David H. Durgee]

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 :
> .
>
>
>
>
>
>>>

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

Re: Crashes

[Frank-Rainer Grahl]

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 :
. 









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

Re: Crashes

[Frank-Rainer Grahl]

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 :
.







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

Re: Crashes

[Ken Rudolph]

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

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

Re: Crashes

[David H. Durgee]

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/185:52 AM
bp-05ab3548-b184-4461-a69d-423500181225
12/24/187:45 PM
bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
12/20/183:00 PM

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

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

Re: Crashes

[Daniel]

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

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

Re: Crashes

[Frank-Rainer Grahl]

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/185:52 AM
bp-05ab3548-b184-4461-a69d-423500181225
12/24/187:45 PM
bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
12/20/183: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 :
.




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

Re: Crashes

[A Williams]

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.

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

Re: Crashes

[Frank-Rainer Grahl]

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.



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

Re: Crashes

[Yamo']

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/185:52 AM
> bp-05ab3548-b184-4461-a69d-423500181225
>   12/24/187:45 PM
> bp-e6cfdc10-c1a3-4cec-8d69-dc4fd0181220
>   12/20/183: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 :
.



-- 

Sorry for possible mistakes in English!
http://pasdenom.info/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[David H. Durgee]

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 :
>> .
>>
>>
>>
>>

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

Re: Crashes

[Frank-Rainer Grahl]

Its not a beta but an unofficial community version. The code has release 
quality but at least two bugs will need to be fixed for the official 
release. Not deal breakers. Geolocation prompting might be broken (was 
just fixed for 2.48) and images vanish from mail sometimes during 
compose when saved as a draft or a template is used.


As usual there are other bugs you can find :)

Not using Fx superlative greatest release ever her but it should be a 
good one and way better than 2.46.


FRG

Ken Rudolph wrote:

Frank-Rainer Grahl wrote:
This seems to be caused by a core bug but I can't access it because it 
is security relevant so not sure if it will be fixed by upgrading to 
the upcoming 2.48.
https://bugzilla.mozilla.org/show_bug.cgi?id=1230817 is a duplicate of 
the bug.


You can upgrade to Adrians unofficial 2.49.1 which will be the next 
version after 2.48:


https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/ 



If you do please backup your profile in case you want to get back to 
2.46 or 2.48. When it finally arrives the official 2.491 will install 
over Adrians fine without the need to do a restore before.


I did this upgrade on 6/27 based on an e-mail, installing the 64bit 
version 2.49.1.  So far it has worked flawlessly including the install, 
with no crashes after 3 day.  I've never worked with a beta before; but 
this has been a good experience for me.


--Ken







FRG

Ken Rudolph wrote:

Mason83 wrote:

On 28/06/2017 00:46, Ken Rudolph wrote:


SM 2.46 (Win-10) has developed the annoying habit of crashing, and
recently way too often.


Please open a browser window, and type about:crashes in the
URL bar. Please copy/paste lines less than 3 months old.

Regards.


bp-a9787be9-a505-403e-9ddf-e5bc70170627
 6/27/173:13 PM
bp-1beb928b-2276-4099-8985-ff0f30170627
 6/27/171:55 PM
bp-2526d098-8115-419e-b8b5-ca5f60170627
 6/27/171:54 PM
bp-29d6f0ce-394d-4b08-be9b-43d8c0170627
 6/26/178:38 PM
bp-5c8bd892-73d8-46f0-8792-6f4e70170626
 6/26/177:49 AM
bp-10068a32-601e-4811-9fc0-1ca4f0170623
 6/23/179:11 AM
bp-3a81a172-2443-43ba-9570-3a0c20170623
 6/23/177:42 AM
bp-5a2d5e67-facc-45a3-bd8a-16ef80170623
 6/22/176:16 PM
bp-97db968a-3e78-4981-ad88-10a120170622
 6/22/1712:19 PM
bp-3e719b0c-e91a-42a1-9c86-ca25e0170621
 6/20/177:21 PM
bp-04fec9a4-24dc-45a1-9d5b-8fe8c0170615
 6/15/173:47 PM
bp-5aa5914b-bf28-44f4-ac50-9efbc0170606
 6/6/1711:14 AM
bp-e09808a2-727b-4d6c-b8cf-d4b3d0170603
 6/3/1712:07 AM
bp-95fe7b67-7e02-4b8f-8d0a-f5e0b0170602
 6/2/1711:15 AM
bp-ceedad10-67b2-42a7-873f-fa8c50170531
 5/30/178:24 PM
bp-2432a2ae-e081-4408-a784-b83de0170531
 5/30/178:09 PM
bp-d5d2c75b-268e-4f05-bd84-ee4370170527
 5/27/1710:58 AM
bp-adcac668-41c7-4271-b9bc-4234a0170527
 5/27/179:38 AM
bp-2b559b38-c78c-4876-9a9c-2380b0170526
 5/26/171:38 PM
bp-6feeadaf-bc81-44f6-8f39-7596b0170526
 5/26/171:27 PM
bp-efc5efb2-1eda-44d5-8cff-b29270170512
 5/12/172:03 PM
bp-07bedba7-0105-4ba2-b431-a736a0170511
 5/11/177:26 AM
bp-50dcc35e-9d8e-4f53-8f4d-f43520170511
 5/11/176:53 AM










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

Re: Crashes

[Ken Rudolph]

Frank-Rainer Grahl wrote:
This seems to be caused by a core bug but I can't access it because it 
is security relevant so not sure if it will be fixed by upgrading to the 
upcoming 2.48.
https://bugzilla.mozilla.org/show_bug.cgi?id=1230817 is a duplicate of 
the bug.


You can upgrade to Adrians unofficial 2.49.1 which will be the next 
version after 2.48:


https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/ 



If you do please backup your profile in case you want to get back to 
2.46 or 2.48. When it finally arrives the official 2.491 will install 
over Adrians fine without the need to do a restore before.


I did this upgrade on 6/27 based on an e-mail, installing the 64bit 
version 2.49.1.  So far it has worked flawlessly including the install, 
with no crashes after 3 day.  I've never worked with a beta before; but 
this has been a good experience for me.


--Ken







FRG

Ken Rudolph wrote:

Mason83 wrote:

On 28/06/2017 00:46, Ken Rudolph wrote:


SM 2.46 (Win-10) has developed the annoying habit of crashing, and
recently way too often.


Please open a browser window, and type about:crashes in the
URL bar. Please copy/paste lines less than 3 months old.

Regards.


bp-a9787be9-a505-403e-9ddf-e5bc70170627
 6/27/173:13 PM
bp-1beb928b-2276-4099-8985-ff0f30170627
 6/27/171:55 PM
bp-2526d098-8115-419e-b8b5-ca5f60170627
 6/27/171:54 PM
bp-29d6f0ce-394d-4b08-be9b-43d8c0170627
 6/26/178:38 PM
bp-5c8bd892-73d8-46f0-8792-6f4e70170626
 6/26/177:49 AM
bp-10068a32-601e-4811-9fc0-1ca4f0170623
 6/23/179:11 AM
bp-3a81a172-2443-43ba-9570-3a0c20170623
 6/23/177:42 AM
bp-5a2d5e67-facc-45a3-bd8a-16ef80170623
 6/22/176:16 PM
bp-97db968a-3e78-4981-ad88-10a120170622
 6/22/1712:19 PM
bp-3e719b0c-e91a-42a1-9c86-ca25e0170621
 6/20/177:21 PM
bp-04fec9a4-24dc-45a1-9d5b-8fe8c0170615
 6/15/173:47 PM
bp-5aa5914b-bf28-44f4-ac50-9efbc0170606
 6/6/1711:14 AM
bp-e09808a2-727b-4d6c-b8cf-d4b3d0170603
 6/3/1712:07 AM
bp-95fe7b67-7e02-4b8f-8d0a-f5e0b0170602
 6/2/1711:15 AM
bp-ceedad10-67b2-42a7-873f-fa8c50170531
 5/30/178:24 PM
bp-2432a2ae-e081-4408-a784-b83de0170531
 5/30/178:09 PM
bp-d5d2c75b-268e-4f05-bd84-ee4370170527
 5/27/1710:58 AM
bp-adcac668-41c7-4271-b9bc-4234a0170527
 5/27/179:38 AM
bp-2b559b38-c78c-4876-9a9c-2380b0170526
 5/26/171:38 PM
bp-6feeadaf-bc81-44f6-8f39-7596b0170526
 5/26/171:27 PM
bp-efc5efb2-1eda-44d5-8cff-b29270170512
 5/12/172:03 PM
bp-07bedba7-0105-4ba2-b431-a736a0170511
 5/11/177:26 AM
bp-50dcc35e-9d8e-4f53-8f4d-f43520170511
 5/11/176:53 AM








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

Re: Crashes

[Frank-Rainer Grahl]

Yes sorry. esr of course.
> [there should be a blank line above this line]

It was during compose. There are still bugs in TB and SM wrt. blank 
lines but got better lately.


FRG

Felix Miata wrote:

https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/

[there should be a blank line above this line]

No 2.49* there, only 2.50 Did you mean?
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-esr-windows32/



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

Re: Crashes

[Felix Miata]

Frank-Rainer Grahl composed on 2017-06-29 08:25 (UTC+0200):

> This seems to be caused by a core bug but I can't access it because it 
> is security relevant so not sure if it will be fixed by upgrading to the 
> upcoming 2.48.
> https://bugzilla.mozilla.org/show_bug.cgi?id=1230817 is a duplicate of 
> the bug.

> You can upgrade to Adrians unofficial 2.49.1 which will be the next 
> version after 2.48:

> https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/

[there should be a blank line above this line]

No 2.49* there, only 2.50 Did you mean?
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-esr-windows32/

> If you do please backup your profile in case you want to get back to 
> 2.46 or 2.48. When it finally arrives the official 2.491 will install 
> over Adrians fine without the need to do a restore before.
> FRG-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[Frank-Rainer Grahl]

This seems to be caused by a core bug but I can't access it because it 
is security relevant so not sure if it will be fixed by upgrading to the 
upcoming 2.48.
https://bugzilla.mozilla.org/show_bug.cgi?id=1230817 is a duplicate of 
the bug.


You can upgrade to Adrians unofficial 2.49.1 which will be the next 
version after 2.48:


https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-release-windows32/

If you do please backup your profile in case you want to get back to 
2.46 or 2.48. When it finally arrives the official 2.491 will install 
over Adrians fine without the need to do a restore before.

FRG

Ken Rudolph wrote:

Mason83 wrote:

On 28/06/2017 00:46, Ken Rudolph wrote:


SM 2.46 (Win-10) has developed the annoying habit of crashing, and
recently way too often.


Please open a browser window, and type about:crashes in the
URL bar. Please copy/paste lines less than 3 months old.

Regards.


bp-a9787be9-a505-403e-9ddf-e5bc70170627
 6/27/173:13 PM
bp-1beb928b-2276-4099-8985-ff0f30170627
 6/27/171:55 PM
bp-2526d098-8115-419e-b8b5-ca5f60170627
 6/27/171:54 PM
bp-29d6f0ce-394d-4b08-be9b-43d8c0170627
 6/26/178:38 PM
bp-5c8bd892-73d8-46f0-8792-6f4e70170626
 6/26/177:49 AM
bp-10068a32-601e-4811-9fc0-1ca4f0170623
 6/23/179:11 AM
bp-3a81a172-2443-43ba-9570-3a0c20170623
 6/23/177:42 AM
bp-5a2d5e67-facc-45a3-bd8a-16ef80170623
 6/22/176:16 PM
bp-97db968a-3e78-4981-ad88-10a120170622
 6/22/1712:19 PM
bp-3e719b0c-e91a-42a1-9c86-ca25e0170621
 6/20/177:21 PM
bp-04fec9a4-24dc-45a1-9d5b-8fe8c0170615
 6/15/173:47 PM
bp-5aa5914b-bf28-44f4-ac50-9efbc0170606
 6/6/1711:14 AM
bp-e09808a2-727b-4d6c-b8cf-d4b3d0170603
 6/3/1712:07 AM
bp-95fe7b67-7e02-4b8f-8d0a-f5e0b0170602
 6/2/1711:15 AM
bp-ceedad10-67b2-42a7-873f-fa8c50170531
 5/30/178:24 PM
bp-2432a2ae-e081-4408-a784-b83de0170531
 5/30/178:09 PM
bp-d5d2c75b-268e-4f05-bd84-ee4370170527
 5/27/1710:58 AM
bp-adcac668-41c7-4271-b9bc-4234a0170527
 5/27/179:38 AM
bp-2b559b38-c78c-4876-9a9c-2380b0170526
 5/26/171:38 PM
bp-6feeadaf-bc81-44f6-8f39-7596b0170526
 5/26/171:27 PM
bp-efc5efb2-1eda-44d5-8cff-b29270170512
 5/12/172:03 PM
bp-07bedba7-0105-4ba2-b431-a736a0170511
 5/11/177:26 AM
bp-50dcc35e-9d8e-4f53-8f4d-f43520170511
 5/11/176:53 AM






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

Re: Crashes

[Mason83]

On 29/06/2017 05:54, Ken Rudolph wrote:
> Mason83 wrote:
>> On 28/06/2017 00:46, Ken Rudolph wrote:
>>
>>> SM 2.46 (Win-10) has developed the annoying habit of crashing, and
>>> recently way too often.
>>
>> Please open a browser window, and type about:crashes in the
>> URL bar. Please copy/paste lines less than 3 months old.
>>
>> Regards.
> 
> bp-a9787be9-a505-403e-9ddf-e5bc70170627
>   6/27/17 3:13 PM
> bp-1beb928b-2276-4099-8985-ff0f30170627
>   6/27/17 1:55 PM
> bp-2526d098-8115-419e-b8b5-ca5f60170627
>   6/27/17 1:54 PM
> bp-29d6f0ce-394d-4b08-be9b-43d8c0170627
>   6/26/17 8:38 PM
> bp-5c8bd892-73d8-46f0-8792-6f4e70170626
>   6/26/17 7:49 AM
> bp-10068a32-601e-4811-9fc0-1ca4f0170623
>   6/23/17 9:11 AM
> bp-3a81a172-2443-43ba-9570-3a0c20170623
>   6/23/17 7:42 AM
> bp-5a2d5e67-facc-45a3-bd8a-16ef80170623
>   6/22/17 6:16 PM
> bp-97db968a-3e78-4981-ad88-10a120170622
>   6/22/17 12:19 PM
> bp-3e719b0c-e91a-42a1-9c86-ca25e0170621
>   6/20/17 7:21 PM
> bp-04fec9a4-24dc-45a1-9d5b-8fe8c0170615
>   6/15/17 3:47 PM
> bp-5aa5914b-bf28-44f4-ac50-9efbc0170606
>   6/6/17  11:14 AM
> bp-e09808a2-727b-4d6c-b8cf-d4b3d0170603
>   6/3/17  12:07 AM
> bp-95fe7b67-7e02-4b8f-8d0a-f5e0b0170602
>   6/2/17  11:15 AM
> bp-ceedad10-67b2-42a7-873f-fa8c50170531
>   5/30/17 8:24 PM
> bp-2432a2ae-e081-4408-a784-b83de0170531
>   5/30/17 8:09 PM
> bp-d5d2c75b-268e-4f05-bd84-ee4370170527
>   5/27/17 10:58 AM
> bp-adcac668-41c7-4271-b9bc-4234a0170527
>   5/27/17 9:38 AM
> bp-2b559b38-c78c-4876-9a9c-2380b0170526
>   5/26/17 1:38 PM
> bp-6feeadaf-bc81-44f6-8f39-7596b0170526
>   5/26/17 1:27 PM
> bp-efc5efb2-1eda-44d5-8cff-b29270170512
>   5/12/17 2:03 PM
> bp-07bedba7-0105-4ba2-b431-a736a0170511
>   5/11/17 7:26 AM
> bp-50dcc35e-9d8e-4f53-8f4d-f43520170511
>   5/11/17 6:53 AM

OK, based on the first 10 crashes, you seem to be hitting
two separate (but maybe related) bugs:

https://crash-stats.mozilla.com/report/index/a9787be9-a505-403e-9ddf-e5bc70170627
https://crash-stats.mozilla.com/report/index/2526d098-8115-419e-b8b5-ca5f60170627
https://crash-stats.mozilla.com/report/index/29d6f0ce-394d-4b08-be9b-43d8c0170627
https://crash-stats.mozilla.com/report/index/10068a32-601e-4811-9fc0-1ca4f0170623
https://crash-stats.mozilla.com/report/index/3a81a172-2443-43ba-9570-3a0c20170623
https://crash-stats.mozilla.com/report/index/97db968a-3e78-4981-ad88-10a120170622
[@ DocumentFrameCallbacks::DocumentFrameCallbacks ]
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0xe5e5e5e9
or sometimes
Crash Address   0xc0

https://crash-stats.mozilla.com/report/index/1beb928b-2276-4099-8985-ff0f30170627
https://crash-stats.mozilla.com/report/index/5c8bd892-73d8-46f0-8792-6f4e70170626
https://crash-stats.mozilla.com/report/index/5a2d5e67-facc-45a3-bd8a-16ef80170623
https://crash-stats.mozilla.com/report/index/3e719b0c-e91a-42a1-9c86-ca25e0170621
[@ TakeFrameRequestCallbacksFrom ]
Crash ReasonEXCEPTION_ACCESS_VIOLATION_EXEC
https://bugzilla.mozilla.org/show_bug.cgi?id=1342823  => NOT PUBLIC (???)


Can you describe what you are doing seconds before the crash?
In other words, how can someone else reproduce this crash.

Regards.


P.S. @FRG => can you see bug 1342823
Was it FIXED recently?
Can you unmask it, or have some mozdev unmask it?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[Ken Rudolph]

Mason83 wrote:

On 28/06/2017 00:46, Ken Rudolph wrote:


SM 2.46 (Win-10) has developed the annoying habit of crashing, and
recently way too often.


Please open a browser window, and type about:crashes in the
URL bar. Please copy/paste lines less than 3 months old.

Regards.


bp-a9787be9-a505-403e-9ddf-e5bc70170627
6/27/17 3:13 PM
bp-1beb928b-2276-4099-8985-ff0f30170627
6/27/17 1:55 PM
bp-2526d098-8115-419e-b8b5-ca5f60170627
6/27/17 1:54 PM
bp-29d6f0ce-394d-4b08-be9b-43d8c0170627
6/26/17 8:38 PM
bp-5c8bd892-73d8-46f0-8792-6f4e70170626
6/26/17 7:49 AM
bp-10068a32-601e-4811-9fc0-1ca4f0170623
6/23/17 9:11 AM
bp-3a81a172-2443-43ba-9570-3a0c20170623
6/23/17 7:42 AM
bp-5a2d5e67-facc-45a3-bd8a-16ef80170623
6/22/17 6:16 PM
bp-97db968a-3e78-4981-ad88-10a120170622
6/22/17 12:19 PM
bp-3e719b0c-e91a-42a1-9c86-ca25e0170621
6/20/17 7:21 PM
bp-04fec9a4-24dc-45a1-9d5b-8fe8c0170615
6/15/17 3:47 PM
bp-5aa5914b-bf28-44f4-ac50-9efbc0170606
6/6/17  11:14 AM
bp-e09808a2-727b-4d6c-b8cf-d4b3d0170603
6/3/17  12:07 AM
bp-95fe7b67-7e02-4b8f-8d0a-f5e0b0170602
6/2/17  11:15 AM
bp-ceedad10-67b2-42a7-873f-fa8c50170531
5/30/17 8:24 PM
bp-2432a2ae-e081-4408-a784-b83de0170531
5/30/17 8:09 PM
bp-d5d2c75b-268e-4f05-bd84-ee4370170527
5/27/17 10:58 AM
bp-adcac668-41c7-4271-b9bc-4234a0170527
5/27/17 9:38 AM
bp-2b559b38-c78c-4876-9a9c-2380b0170526
5/26/17 1:38 PM
bp-6feeadaf-bc81-44f6-8f39-7596b0170526
5/26/17 1:27 PM
bp-efc5efb2-1eda-44d5-8cff-b29270170512
5/12/17 2:03 PM
bp-07bedba7-0105-4ba2-b431-a736a0170511
5/11/17 7:26 AM
bp-50dcc35e-9d8e-4f53-8f4d-f43520170511
5/11/17 6:53 AM




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

Re: Crashes (W10 pro, 64b, desktop)

[Mason83]

On 28/06/2017 03:21, bo1953 wrote:

> I, too, have a great deal of crashes over the last month or so.

Please open a browser window, and type about:crashes in the
URL bar. Please copy/paste lines less than 3 months old.

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

Re: Crashes

[Mason83]

On 28/06/2017 00:46, Ken Rudolph wrote:

> SM 2.46 (Win-10) has developed the annoying habit of crashing, and 
> recently way too often.

Please open a browser window, and type about:crashes in the
URL bar. Please copy/paste lines less than 3 months old.

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

Re: Crashes (W10 pro, 64b, desktop)

[Frank-Rainer Grahl]

Do you have a crash id?

Official 2.48 building will start this week.  I know late but can't be 
helped. At least 2 top crashers will be gone from it which were in the 
Beta. Next is 2.49.1 soon after but i do better not give out a date. 
Real life interferes with building too often :)


FRG

bo1953 wrote:



I, too, have a great deal of crashes over the last month or so. Thought 
it was just me.


It happens when at no particular website, just determines it is time to 
crash and does so...


Can be very annoying if trying to complete a transaction or in the 
middle of something for a client.


Suggestions??

TIA - bo1953


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

Re: Crashes

[Arnie Goetchius]

Ken Rudolph wrote:
> SM 2.46 (Win-10) has developed the annoying habit of crashing, and recently 
> way too often.  I
> immediately get the window that allows SM to restore all tabs and windows; 
> but when I do entries in
> the process of being written have disappeared.  This is especially annoying 
> in Composer when I'm
> editing a web site with the HTML composer included with SeaMonkey.  In fact 
> it is more than
> annoying; it's something that I have to cope with ASAP (yes, frequent saving 
> does help a bit; but if
> I forget it is a disaster.)
> 
> So, the question:  is there a stand-alone Mozilla web site composing app 
> available that wouldn't be
> subject to a SM crash?  It would be nice if such a thing existed in Firefox 
> or Thunderbird, or as a
> separate program.  After almost 20 years of using Netscape and SeaMonkey to 
> edit my web site I can't
> imagine using another program; but if Mozilla doesn't have one, can somebody 
> suggest a similar
> "free" HTML editing program that would work just as efficiently?
> 
> Thanks much.
> 
I use Pagebreeze http://www.pagebreeze.com/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes (W10 pro, 64b, desktop)

[WaltS48]

On 6/27/17 9:21 PM, bo1953 wrote:

Ken Rudolph wrote:

SM 2.46 (Win-10) has developed the annoying habit of crashing, and
recently way too often.  I immediately get the window that allows SM to
restore all tabs and windows; but when I do entries in the process of
being written have disappeared.  This is especially annoying in Composer
when I'm editing a web site with the HTML composer included with
SeaMonkey.  In fact it is more than annoying; it's something that I have
to cope with ASAP (yes, frequent saving does help a bit; but if I forget
it is a disaster.)

So, the question:  is there a stand-alone Mozilla web site composing app
available that wouldn't be subject to a SM crash?  It would be nice if
such a thing existed in Firefox or Thunderbird, or as a separate
program.  After almost 20 years of using Netscape and SeaMonkey to edit
my web site I can't imagine using another program; but if Mozilla
doesn't have one, can somebody suggest a similar "free" HTML editing
program that would work just as efficiently?

Thanks much.



I, too, have a great deal of crashes over the last month or so. Thought 
it was just me.


It happens when at no particular website, just determines it is time to 
crash and does so...


Can be very annoying if trying to complete a transaction or in the 
middle of something for a client.


Suggestions??

TIA - bo1953



Start your own thread and don't hijack one about a completely different 
problem is mine.



--
Go Bucs!
Coexist 
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[WaltS48]

On 6/27/17 6:46 PM, Ken Rudolph wrote:
SM 2.46 (Win-10) has developed the annoying habit of crashing, and 
recently way too often.  I immediately get the window that allows SM to 
restore all tabs and windows; but when I do entries in the process of 
being written have disappeared.  This is especially annoying in Composer 
when I'm editing a web site with the HTML composer included with 
SeaMonkey.  In fact it is more than annoying; it's something that I have 
to cope with ASAP (yes, frequent saving does help a bit; but if I forget 
it is a disaster.)


So, the question:  is there a stand-alone Mozilla web site composing app 
available that wouldn't be subject to a SM crash?  It would be nice if 
such a thing existed in Firefox or Thunderbird, or as a separate 
program.  After almost 20 years of using Netscape and SeaMonkey to edit 
my web site I can't imagine using another program; but if Mozilla 
doesn't have one, can somebody suggest a similar "free" HTML editing 
program that would work just as efficiently?


Thanks much.



Have you tried loading the web page into the browser, use Tools > Web 
Development > Toggle Tools and editing it from there?


Knowledge of HTML and CSS may be required.

--
Go Bucs!
Coexist 
National Popular Vote 
Ubuntu 16.04LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes (W10 pro, 64b, desktop)

[bo1953]

Ken Rudolph wrote:

SM 2.46 (Win-10) has developed the annoying habit of crashing, and
recently way too often.  I immediately get the window that allows SM to
restore all tabs and windows; but when I do entries in the process of
being written have disappeared.  This is especially annoying in Composer
when I'm editing a web site with the HTML composer included with
SeaMonkey.  In fact it is more than annoying; it's something that I have
to cope with ASAP (yes, frequent saving does help a bit; but if I forget
it is a disaster.)

So, the question:  is there a stand-alone Mozilla web site composing app
available that wouldn't be subject to a SM crash?  It would be nice if
such a thing existed in Firefox or Thunderbird, or as a separate
program.  After almost 20 years of using Netscape and SeaMonkey to edit
my web site I can't imagine using another program; but if Mozilla
doesn't have one, can somebody suggest a similar "free" HTML editing
program that would work just as efficiently?

Thanks much.



I, too, have a great deal of crashes over the last month or so. Thought 
it was just me.


It happens when at no particular website, just determines it is time to 
crash and does so...


Can be very annoying if trying to complete a transaction or in the 
middle of something for a client.


Suggestions??

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

Re: Crashes

[Richard Alan]

Ken Rudolph wrote:

> but if Mozilla doesn't have one,
> can somebody suggest a similar "free" HTML editing program that would
> work just as efficiently?

Since Composer is decades old, without updates, you may like BlueGriffon 
which is an offshoot and has been in development for many years. It's 
latest update was Feb 24, 2017. There are free, and paid, versions. The 
free one doesn't include the CSS editor. (Do you use CSS?)

https://en.wikipedia.org/wiki/BlueGriffon

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

Re: Crashes

[Lee]

On 6/27/17, Ken Rudolph  wrote:
> SM 2.46 (Win-10) has developed the annoying habit of crashing, and
> recently way too often.  I immediately get the window that allows SM to
> restore all tabs and windows; but when I do entries in the process of
> being written have disappeared.  This is especially annoying in Composer
> when I'm editing a web site with the HTML composer included with
> SeaMonkey.  In fact it is more than annoying; it's something that I have
> to cope with ASAP (yes, frequent saving does help a bit; but if I forget
> it is a disaster.)

just out of curiosity - are you using the 32 or 64bit version of SeaMonkey?

> So, the question:  is there a stand-alone Mozilla web site composing app
> available that wouldn't be subject to a SM crash?  It would be nice if
> such a thing existed in Firefox or Thunderbird, or as a separate
> program.  After almost 20 years of using Netscape and SeaMonkey to edit
> my web site I can't imagine using another program; but if Mozilla
> doesn't have one, can somebody suggest a similar "free" HTML editing
> program that would work just as efficiently?

You can try searching the archives or take a look at
  https://en.wikipedia.org/wiki/Comparison_of_HTML_editors
the question seems to come up all too often ... with no satisfactory answer :(

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

Re: Crashes

[TCW]

On 1/19/2017 8:54 AM, JAS wrote:

David E. Ross wrote:

On 1/18/2017 6:16 AM, TCW wrote [in part]:

Also, one of the crashing DLLs I noticed was Malwarebytes Anti-Exploit.
I don't know if there's a newer version of this app but if so, see if
updating it will help. Also, try running in Safe Mode and see if you
still get crashes.


Malwarebytes has been having such serious problems with its version 3
that they advised me to revert to the last of version 2.


I also saw that they were having problems, I think I may revert back to
Ver. 2
On the drivers advice I went to Intel and found the more current drivers
and tried to install three different ones and received a pop up that I
had a customized chip by HP and they could not be installed.


Cursed HP! How can it be custom when the CPU is built by Intel and the 
VGA resides on the CPU. Nonsense. I bet if you remove the driver and 
then try the Intel drivers it'll work.

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

Re: Crashes

[Frank-Rainer Grahl]

Remove the HP drivers first. Use ddu to clear them out if it still 
doesn't work. Was the same with my T61 where I originally had the lenovo 
drivers installed.


FRG

JAS wrote:

David E. Ross wrote:

On 1/18/2017 6:16 AM, TCW wrote [in part]:
On the drivers advice I went to Intel and found the more current drivers 
and tried to install three different ones and received a pop up that I 
had a customized chip by HP and they could not be installed.


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

Re: Crashes

[JAS]

David E. Ross wrote:

On 1/18/2017 6:16 AM, TCW wrote [in part]:

Also, one of the crashing DLLs I noticed was Malwarebytes Anti-Exploit.
I don't know if there's a newer version of this app but if so, see if
updating it will help. Also, try running in Safe Mode and see if you
still get crashes.


Malwarebytes has been having such serious problems with its version 3
that they advised me to revert to the last of version 2.

I also saw that they were having problems, I think I may revert back to 
Ver. 2
On the drivers advice I went to Intel and found the more current drivers 
and tried to install three different ones and received a pop up that I 
had a customized chip by HP and they could not be installed.

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

Re: Crashes

[TCW]

On 1/18/2017 5:57 PM, David E. Ross wrote:

On 1/18/2017 6:16 AM, TCW wrote [in part]:

Also, one of the crashing DLLs I noticed was Malwarebytes Anti-Exploit.
I don't know if there's a newer version of this app but if so, see if
updating it will help. Also, try running in Safe Mode and see if you
still get crashes.


Malwarebytes has been having such serious problems with its version 3
that they advised me to revert to the last of version 2.


I too tried 3.x. I reverted back to 2.x as well.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[David E. Ross]

On 1/18/2017 6:16 AM, TCW wrote [in part]:
> Also, one of the crashing DLLs I noticed was Malwarebytes Anti-Exploit. 
> I don't know if there's a newer version of this app but if so, see if 
> updating it will help. Also, try running in Safe Mode and see if you 
> still get crashes.

Malwarebytes has been having such serious problems with its version 3
that they advised me to revert to the last of version 2.

-- 
David E. Ross


When the President of the United States makes a statement of
national importance, I want to see his face as he is talking.
At the least, I want to hear his voice.

Donald:  Stop tweeting.  Otherwise, how do we know the message
really comes from you?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[JAS]

TCW wrote:

On 1/17/2017 8:40 PM, JAS wrote:

TCW wrote:

On 1/16/2017 11:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher
the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101
Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116




http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116




http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110




http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109





Thanks
JAS


From your crash report: Available Physical Memory: 5,169,344,512 bytes
(4.81 GB)huh? How is this even possible? Available physical memory
is at 4.81GB on x86? Do you have 8GB installed on an x86 machine? PAE
running? I see you page file is at 12GB so I am assuming you have 8GB
installed (and MS's 1.5xRAM rule applies). Did you run a memtest lately?

I do have 8GB of ram installed,it came set up that way,HP 4540 is 64/32
bit and I run mostly 32 bit programs on it. I have ran a Mem Test and no
error or abnormality were found. I have reverted back to SM 2.47 and
have had no crashes since. On the SM2.48 I also could not play any flash
videos.


Hmm, I am running the 64-bit 2.48 build from AKalla and it's been pretty
solid. I also have the newest flash from last week (24.0.0.194). Have
you tried giving the 2.48 64-bit build a shot?

You have an Intel HD4000 for VGA right? Try updating to version
15.33.43.4425 (from Intel's site, from 2016, or version 15.33.44.4491
from Station Drivers, what I have running) as the drivers you have
(8.15.10.2712, from 2012) are pretty old. Could be just a driver issue
so try and rule that out

Also, one of the crashing DLLs I noticed was Malwarebytes Anti-Exploit.
I don't know if there's a newer version of this app but if so, see if
updating it will help. Also, try running in Safe Mode and see if you
still get crashes.

Yhanks, I will check to see if the drivers are up to date.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[JAS]

NoOp wrote:

On 1/16/2017 9:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109

Thanks
JAS



Maybe related for crash 1,2, and 4:

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

Hit this a couple of times filtering folders using quick search.
MOZ_CRASH ReasonElementAt(aIndex = 17, aLength = 17)

Status: RESOLVED DUPLICATE of bug 1311672
https://bugzilla.mozilla.org/show_bug.cgi?id=1311672


Thanks, I read up on it.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[NoOp]

On 1/16/2017 9:08 AM, JAS wrote:
> I have had several crashes lately and wonder if someone can decipher the 
> crash reports? Using SM 2.48 on Win 7 Pro
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 
> SeaMonkey/2.48 - Build ID: 20161208025245
> 
> http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
> http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
> http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
> http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109
> 
> Thanks
> JAS
> 

Maybe related for crash 1,2, and 4:

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

Hit this a couple of times filtering folders using quick search.
MOZ_CRASH ReasonElementAt(aIndex = 17, aLength = 17)

Status: RESOLVED DUPLICATE of bug 1311672
https://bugzilla.mozilla.org/show_bug.cgi?id=1311672
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[Mason83]

On 16/01/2017 18:08, JAS wrote:

> I have had several crashes lately and wonder if someone can decipher the 
> crash reports? Using SM 2.48 on Win 7 Pro
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 
> SeaMonkey/2.48 - Build ID: 20161208025245
> 
> http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
> http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
> http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
> http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109

This 2.48 build has debug symbols:

https://archive.mozilla.org/pub/seamonkey/nightly/latest-comm-aurora/seamonkey-2.48a2.en-US.win32.installer.exe

If you can consistently reproduce the crash, it might be
useful to crash a few times using that build, to create
"good" crash reports (with a back trace).

Regards.

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

Re: Crashes

[Mason83]

On 17/01/2017 19:46, TCW wrote:

>  From your crash report: Available Physical Memory: 5,169,344,512 bytes 
> (4.81 GB)huh? How is this even possible? Available physical memory 
> is at 4.81GB on x86? Do you have 8GB installed on an x86 machine? PAE 
> running? I see you page file is at 12GB so I am assuming you have 8GB 
> installed (and MS's 1.5xRAM rule applies). Did you run a memtest lately?

He's just running the 32-bit version on a 64-bit kernel.

And I think "Available Physical Memory" represents "free" memory,
after all the other apps (and the kernel) got what they needed.

Regards.

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

Re: Crashes

[TCW]

On 1/17/2017 8:40 PM, JAS wrote:

TCW wrote:

On 1/16/2017 11:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116



http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116



http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110



http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109




Thanks
JAS


From your crash report: Available Physical Memory: 5,169,344,512 bytes
(4.81 GB)huh? How is this even possible? Available physical memory
is at 4.81GB on x86? Do you have 8GB installed on an x86 machine? PAE
running? I see you page file is at 12GB so I am assuming you have 8GB
installed (and MS's 1.5xRAM rule applies). Did you run a memtest lately?

I do have 8GB of ram installed,it came set up that way,HP 4540 is 64/32
bit and I run mostly 32 bit programs on it. I have ran a Mem Test and no
error or abnormality were found. I have reverted back to SM 2.47 and
have had no crashes since. On the SM2.48 I also could not play any flash
videos.


Hmm, I am running the 64-bit 2.48 build from AKalla and it's been pretty 
solid. I also have the newest flash from last week (24.0.0.194). Have 
you tried giving the 2.48 64-bit build a shot?


You have an Intel HD4000 for VGA right? Try updating to version 
15.33.43.4425 (from Intel's site, from 2016, or version 15.33.44.4491 
from Station Drivers, what I have running) as the drivers you have 
(8.15.10.2712, from 2012) are pretty old. Could be just a driver issue 
so try and rule that out


Also, one of the crashing DLLs I noticed was Malwarebytes Anti-Exploit. 
I don't know if there's a newer version of this app but if so, see if 
updating it will help. Also, try running in Safe Mode and see if you 
still get crashes.

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

Re: Crashes

[JAS]

TCW wrote:

On 1/16/2017 11:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116


http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116


http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110


http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109



Thanks
JAS


From your crash report: Available Physical Memory: 5,169,344,512 bytes
(4.81 GB)huh? How is this even possible? Available physical memory
is at 4.81GB on x86? Do you have 8GB installed on an x86 machine? PAE
running? I see you page file is at 12GB so I am assuming you have 8GB
installed (and MS's 1.5xRAM rule applies). Did you run a memtest lately?
I do have 8GB of ram installed,it came set up that way,HP 4540 is 64/32 
bit and I run mostly 32 bit programs on it. I have ran a Mem Test and no 
error or abnormality were found. I have reverted back to SM 2.47 and 
have had no crashes since. On the SM2.48 I also could not play any flash 
videos.

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

Re: Crashes

[TCW]

On 1/16/2017 11:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116

http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116

http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110

http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109


Thanks
JAS


From your crash report: Available Physical Memory: 5,169,344,512 bytes 
(4.81 GB)huh? How is this even possible? Available physical memory 
is at 4.81GB on x86? Do you have 8GB installed on an x86 machine? PAE 
running? I see you page file is at 12GB so I am assuming you have 8GB 
installed (and MS's 1.5xRAM rule applies). Did you run a memtest lately?

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

Re: Crashes

[Frank-Rainer Grahl]

> I know, and they don't even have a Beta build yet. Wonder what the reason for
> that is, or did I just miss it at:

Beta progress is tracked in Bug 1328886:

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

As usual build config changes and the odd bug or two. Nothing serious so far. 
It might still not be possible to include the 'missing' add ons again but 
taking them out in 2.46 seems not to have caused big problems. If this ends up 
as a release and not beta we will see soon. If release we will probably see a 
2.49 beta afterwards.


SeaMonkey 2.48 will likely be the last official version build with gtk2 so if 
you have problems with gtk3 and have not filed a bug better do it now. gtk2 is 
now officially dead with 2.50a1 and up. Mozilla removed the support to build 
it with gtk2.


FRG

WaltS48 wrote:

On 01/16/2017 05:36 PM, David E. Ross wrote:

On 1/16/2017 1:40 PM, WaltS48 wrote:

On 01/16/2017 02:56 PM, David E. Ross wrote:

On 1/16/2017 9:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116 

http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116 

http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110 

http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109 



Thanks
JAS



SeaMonkey 2.48 is still being developed.  Thus, crashes might be
expected.  Report them at  so
that the developers can fix them before 2.48 is released to end-users.




That might not do any good, as there is no SeaMonkey 2.48 from the
SeaMonkey Project.

Nightly is 2.50a1


Aurora is 2.49a2


Beta is 2.46


Release is 2.46 



According to the minutes of the 10 January 2017 SeaMonkey Status
Meeting, the next release is 2.48.  See
.




I know, and they don't even have a Beta build yet. Wonder what the reason for 
that is, or did I just miss it at:




Maybe they are waiting for next weeks merges, when 2.50a1 becomes 2.51a1, 
2.49a2 becomes 2.50a2, 2.4?b(x) should be 2.49b1 and release would be 2.48. 


Well, Firefox Beta merged to release today, so 51.0rc should be out tomorrow. 
Isn't that what 2.48 is based on?




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

Re: Crashes

[WaltS48]

On 01/16/2017 05:36 PM, David E. Ross wrote:

On 1/16/2017 1:40 PM, WaltS48 wrote:

On 01/16/2017 02:56 PM, David E. Ross wrote:

On 1/16/2017 9:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109

Thanks
JAS



SeaMonkey 2.48 is still being developed.  Thus, crashes might be
expected.  Report them at  so
that the developers can fix them before 2.48 is released to end-users.




That might not do any good, as there is no SeaMonkey 2.48 from the
SeaMonkey Project.

Nightly is 2.50a1


Aurora is 2.49a2


Beta is 2.46


Release is 2.46 



According to the minutes of the 10 January 2017 SeaMonkey Status
Meeting, the next release is 2.48.  See
.




I know, and they don't even have a Beta build yet. Wonder what the 
reason for that is, or did I just miss it at:




Maybe they are waiting for next weeks merges, when 2.50a1 becomes 
2.51a1, 2.49a2 becomes 2.50a2, 2.4?b(x) should be 2.49b1 and release 
would be 2.48. 


Well, Firefox Beta merged to release today, so 51.0rc should be out 
tomorrow. Isn't that what 2.48 is based on?


--
Visit Pittsburgh 
Coexist 
Ubuntu 16.04LTS
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[David E. Ross]

On 1/16/2017 1:40 PM, WaltS48 wrote:
> On 01/16/2017 02:56 PM, David E. Ross wrote:
>> On 1/16/2017 9:08 AM, JAS wrote:
>>> I have had several crashes lately and wonder if someone can decipher the
>>> crash reports? Using SM 2.48 on Win 7 Pro
>>> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
>>> SeaMonkey/2.48 - Build ID: 20161208025245
>>>
>>> http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
>>> http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
>>> http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
>>> http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109
>>>
>>> Thanks
>>> JAS
>>>
>>
>> SeaMonkey 2.48 is still being developed.  Thus, crashes might be
>> expected.  Report them at  so
>> that the developers can fix them before 2.48 is released to end-users.
>>
> 
> 
> That might not do any good, as there is no SeaMonkey 2.48 from the 
> SeaMonkey Project.
> 
> Nightly is 2.50a1 
> 
> 
> Aurora is 2.49a2 
> 
> 
> Beta is 2.46 
> 
> 
> Release is 2.46 
> 

According to the minutes of the 10 January 2017 SeaMonkey Status
Meeting, the next release is 2.48.  See
.

-- 
David E. Ross


When the President of the United States makes a statement of
national importance, I want to see his face as he is talking.
At the least, I want to hear his voice.

Donald:  Stop tweeting.  Otherwise, how do we know the message
really comes from you?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[WaltS48]

On 01/16/2017 02:56 PM, David E. Ross wrote:

On 1/16/2017 9:08 AM, JAS wrote:

I have had several crashes lately and wonder if someone can decipher the
crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109

Thanks
JAS



SeaMonkey 2.48 is still being developed.  Thus, crashes might be
expected.  Report them at  so
that the developers can fix them before 2.48 is released to end-users.




That might not do any good, as there is no SeaMonkey 2.48 from the 
SeaMonkey Project.


Nightly is 2.50a1 



Aurora is 2.49a2 



Beta is 2.46 



Release is 2.46 

--
Visit Pittsburgh 
Coexist 
Ubuntu 16.04LTS
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[David E. Ross]

On 1/16/2017 9:08 AM, JAS wrote:
> I have had several crashes lately and wonder if someone can decipher the 
> crash reports? Using SM 2.48 on Win 7 Pro
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 
> SeaMonkey/2.48 - Build ID: 20161208025245
> 
> http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116
> http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116
> http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110
> http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109
> 
> Thanks
> JAS
> 

SeaMonkey 2.48 is still being developed.  Thus, crashes might be
expected.  Report them at  so
that the developers can fix them before 2.48 is released to end-users.

-- 
David E. Ross


When the President of the United States makes a statement of
national importance, I want to see his face as he is talking.
At the least, I want to hear his voice.

Donald:  Stop tweeting.  Otherwise, how do we know the message
really comes from you?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes

[JAS]

Frank-Rainer Grahl wrote:

Looks like these come from Adrians or local builds. Unfortunately they
do not have symbols so the crash reports are almost useless. Do you know
what you did when SeaMonkey crashed?

It sounds like the same problem mason385 reported. There are a few bug
reports against the mailnews component open with a similar crash reason.

FRG

JAS wrote:

I have had several crashes lately and wonder if someone can decipher
the crash reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101
Firefox/51.0 SeaMonkey/2.48 - Build ID: 20161208025245

http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116

http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116

http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110

http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109


Thanks
JAS


I was starting to compose a new email when the last on happened and the 
one prior i clicked on an email to read it.

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

Re: Crashes

[Frank-Rainer Grahl]

Looks like these come from Adrians or local builds. Unfortunately they do not 
have symbols so the crash reports are almost useless. Do you know what you did 
when SeaMonkey crashed?


It sounds like the same problem mason385 reported. There are a few bug reports 
against the mailnews component open with a similar crash reason.


FRG

JAS wrote:
I have had several crashes lately and wonder if someone can decipher the crash 
reports? Using SM 2.48 on Win 7 Pro
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 
SeaMonkey/2.48 - Build ID: 20161208025245


http://crash-stats.mozilla.com/report/index/bp-a263dd8f-403a-4053-bfb0-fe7d32170116 

http://crash-stats.mozilla.com/report/index/bp-a6c8d7c6-2968-4f01-989f-8a9b42170116 

http://crash-stats.mozilla.com/report/index/bp-c827a390-641a-497f-ba0b-33c202170110 

http://crash-stats.mozilla.com/report/index/bp-83b3296e-598a-4ab6-8601-f22a32170109 



Thanks
JAS


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

Re: Crashes

[Chris Ilias]

On 12-06-01 10:10 PM, Alex wrote:

On 6/1/2012 7:47 PM, Chris Ilias wrote:

On 12-06-01 6:06 PM, Alex wrote:

In the last several months since upgrading to new version my SM has been
randomly crashing. I tried to run it in safe mode but problem persisted.
I was hoping that with new upgrade it's be resolved but nothing changed.
The crashes happening on my laptop, notebook and desktop with Windows 7
(64 bit). I have been using SM and previously Netscape since 90's and
this was major disappointment. I finally gave up and installed FF and TB
and so far all runs fine.


Does the Mozilla Crash Reporter come up? If so, open SeaMonkey, go to
Help--Troubleshooting_Information, and click on about:crashes. From
there, click on your latest crash reports, and tell us your latest crash
IDs. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.


Chris/
Here are the numbers:
17e72863-91ee-49a9-960d-4fb362120317
fbdb8bee-05a6-4cc6-84a6-ac5a12120316
16a867f0-2e99-46fd-b293-13aca2120316
02a99b8c-938d-438b-8dc1-bf9df2120313
0f502d08-a3c9-4d78-8c38-88ae22120313
b695454c-9471-42b4-bea0-02a8e2120312
acede0f4-92b9-40ce-a440-9470f2120312
eef9489f-3e9c-4e4b-a7dd-cdd1b2120311



Those crashes happened in March and earlier, so I assume those aren't 
the ones that triggered you to post in here.


If it's still happening in safe mode, try this:
1. Uninstall SeaMonkey
2. Reboot your computer
3. Delete the directory: C:\Program Files\SeaMonkey\ (it may be 
different on 64 bit version)

4. Re-install SeaMonkey

--
Chris Ilias http://ilias.ca
Newsgroup moderator


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

Re: Crashes

[Alex]

On 6/2/2012 3:49 PM, Chris Ilias wrote:

On 12-06-01 10:10 PM, Alex wrote:

On 6/1/2012 7:47 PM, Chris Ilias wrote:

On 12-06-01 6:06 PM, Alex wrote:

In the last several months since upgrading to new version my SM has
been
randomly crashing. I tried to run it in safe mode but problem
persisted.
I was hoping that with new upgrade it's be resolved but nothing
changed.
The crashes happening on my laptop, notebook and desktop with Windows 7
(64 bit). I have been using SM and previously Netscape since 90's and
this was major disappointment. I finally gave up and installed FF
and TB
and so far all runs fine.


Does the Mozilla Crash Reporter come up? If so, open SeaMonkey, go to
Help--Troubleshooting_Information, and click on about:crashes. From
there, click on your latest crash reports, and tell us your latest crash
IDs. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.


Chris/
Here are the numbers:
17e72863-91ee-49a9-960d-4fb362120317
fbdb8bee-05a6-4cc6-84a6-ac5a12120316
16a867f0-2e99-46fd-b293-13aca2120316
02a99b8c-938d-438b-8dc1-bf9df2120313
0f502d08-a3c9-4d78-8c38-88ae22120313
b695454c-9471-42b4-bea0-02a8e2120312
acede0f4-92b9-40ce-a440-9470f2120312
eef9489f-3e9c-4e4b-a7dd-cdd1b2120311



Those crashes happened in March and earlier, so I assume those aren't
the ones that triggered you to post in here.

If it's still happening in safe mode, try this:
1. Uninstall SeaMonkey
2. Reboot your computer
3. Delete the directory: C:\Program Files\SeaMonkey\ (it may be
different on 64 bit version)
4. Re-install SeaMonkey


Chris,

Here are the latest ones:

bp-29294740-217b-473a-b1e3-4ff232120601
bp-f1de6d80-85e2-42c5-a60f-0114e2120601
bp-ec03c7e1-3d4e-4c11-a65b-3dfa22120601
bp-32346e6c-ce7d-4e61-b26d-e3b242120530
bp-4239920e-9017-4930-be61-4525f2120530

In the past I tried to re-install SM with re-booting but did not delete 
its directory. It did not help.


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

Re: Crashes

[Eric]

Alex wrote:

On 6/2/2012 3:49 PM, Chris Ilias wrote:

On 12-06-01 10:10 PM, Alex wrote:

On 6/1/2012 7:47 PM, Chris Ilias wrote:

On 12-06-01 6:06 PM, Alex wrote:

In the last several months since upgrading to new version my SM has
been
randomly crashing. I tried to run it in safe mode but problem
persisted.
I was hoping that with new upgrade it's be resolved but nothing
changed.
The crashes happening on my laptop, notebook and desktop with
Windows 7
(64 bit). I have been using SM and previously Netscape since 90's and
this was major disappointment. I finally gave up and installed FF
and TB
and so far all runs fine.


Does the Mozilla Crash Reporter come up? If so, open SeaMonkey, go to
Help--Troubleshooting_Information, and click on about:crashes. From
there, click on your latest crash reports, and tell us your latest
crash
IDs. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.


Chris/
Here are the numbers:
17e72863-91ee-49a9-960d-4fb362120317
fbdb8bee-05a6-4cc6-84a6-ac5a12120316
16a867f0-2e99-46fd-b293-13aca2120316
02a99b8c-938d-438b-8dc1-bf9df2120313
0f502d08-a3c9-4d78-8c38-88ae22120313
b695454c-9471-42b4-bea0-02a8e2120312
acede0f4-92b9-40ce-a440-9470f2120312
eef9489f-3e9c-4e4b-a7dd-cdd1b2120311



Those crashes happened in March and earlier, so I assume those aren't
the ones that triggered you to post in here.

If it's still happening in safe mode, try this:
1. Uninstall SeaMonkey
2. Reboot your computer
3. Delete the directory: C:\Program Files\SeaMonkey\ (it may be
different on 64 bit version)
4. Re-install SeaMonkey


Chris,

Here are the latest ones:

bp-29294740-217b-473a-b1e3-4ff232120601
bp-f1de6d80-85e2-42c5-a60f-0114e2120601
bp-ec03c7e1-3d4e-4c11-a65b-3dfa22120601
bp-32346e6c-ce7d-4e61-b26d-e3b242120530
bp-4239920e-9017-4930-be61-4525f2120530

In the past I tried to re-install SM with re-booting but did not delete
its directory. It did not help.

Alex
I would do what Chris Suggested, however, back up your profile using 
Mozilla backup.  Then you can safely remove the directory and re install 
all your information from the backup.


Also submit your issue to the Seamonkey builders team with all info 
about your system, build, and what you were doing.  More information is 
better for them.


HTH

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

Re: Crashes

[Chris Ilias]

On 12-06-01 6:06 PM, Alex wrote:

In the last several months since upgrading to new version my SM has been
randomly crashing. I tried to run it in safe mode but problem persisted.
I was hoping that with new upgrade it's be resolved but nothing changed.
The crashes happening on my laptop, notebook and desktop with Windows 7
(64 bit). I have been using SM and previously Netscape since 90's and
this was major disappointment. I finally gave up and installed FF and TB
and so far all runs fine.


Does the Mozilla Crash Reporter come up? If so, open SeaMonkey, go to 
Help--Troubleshooting_Information, and click on about:crashes. From 
there, click on your latest crash reports, and tell us your latest crash 
IDs. We can then look at the data specific to your crash and have a 
better idea of what is causing the problem.


--
Chris Ilias http://ilias.ca
Newsgroup moderator


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

Re: Crashes

[Alex]

On 6/1/2012 7:47 PM, Chris Ilias wrote:

On 12-06-01 6:06 PM, Alex wrote:

In the last several months since upgrading to new version my SM has been
randomly crashing. I tried to run it in safe mode but problem persisted.
I was hoping that with new upgrade it's be resolved but nothing changed.
The crashes happening on my laptop, notebook and desktop with Windows 7
(64 bit). I have been using SM and previously Netscape since 90's and
this was major disappointment. I finally gave up and installed FF and TB
and so far all runs fine.


Does the Mozilla Crash Reporter come up? If so, open SeaMonkey, go to
Help--Troubleshooting_Information, and click on about:crashes. From
there, click on your latest crash reports, and tell us your latest crash
IDs. We can then look at the data specific to your crash and have a
better idea of what is causing the problem.


Chris/
Here are the numbers:
17e72863-91ee-49a9-960d-4fb362120317
fbdb8bee-05a6-4cc6-84a6-ac5a12120316
16a867f0-2e99-46fd-b293-13aca2120316
02a99b8c-938d-438b-8dc1-bf9df2120313
0f502d08-a3c9-4d78-8c38-88ae22120313
b695454c-9471-42b4-bea0-02a8e2120312
acede0f4-92b9-40ce-a440-9470f2120312
eef9489f-3e9c-4e4b-a7dd-cdd1b2120311

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

Re: Crashes When Printing

[cyberzen]

Chris Ilias a écrit :

On 11-11-02 12:01 AM, Sandy Pamin wrote:

ID: d07f1d26-9787-4ff2-9637-a2d9f201
Signature: F_1359172165


That crash is caused by the Flash plugin.
I don't remember if the plugin crash protection feature was implemented
before or after SM 2.0.14; but you should try upgrading both SeaMonkey
and Flash.

still in 2.0.14 myself I had some crashes in flash, but it is not the 
real culprit, but the install proc of adobe, I am solved by uninstalling 
and reinstalling flash whith a fresh download from adobe, they seem to 
have improved it silently.


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

Re: Crashes When Printing

[Chris Ilias]

On 11-11-02 12:01 AM, Sandy Pamin wrote:

ID: d07f1d26-9787-4ff2-9637-a2d9f201
Signature: F_1359172165


That crash is caused by the Flash plugin.
I don't remember if the plugin crash protection feature was implemented 
before or after SM 2.0.14; but you should try upgrading both SeaMonkey 
and Flash.


--
Chris Ilias http://ilias.ca
Mailing list/Newsgroup moderator
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes When Printing

[Robert Kaiser]

Chris Ilias schrieb:

I don't remember if the plugin crash protection feature was implemented
before or after SM 2.0.14


After. You need 2.1 or higher to have plugin crash protection. And we 
have been fixing a lot of crashes in recent times, so anyone seeing 
crashes should get to at least the current release (2.4.1 at this 
moment) as soon as possible.

I also would advise to update Flash to 11.0.

Robert Kaiser

--
Note that any statements of mine - no matter how passionate - are never 
meant to be offensive but very often as food for thought or possible 
arguments that we as a community should think about. And most of the 
time, I even appreciate irony and fun! :)

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

Re: Crashes When Printing

[Robert Kaiser]

Sandy Pamin schrieb:

Seamonkey 2.0.14 has been crashing a lot lately when trying to print.


Please try 2.4.1, it's easily possible that this has been fixed there. 
We are steadily working on fixing crashes in all Mozilla products.


Robert Kaiser


--
Note that any statements of mine - no matter how passionate - are never 
meant to be offensive but very often as food for thought or possible 
arguments that we as a community should think about. And most of the 
time, I even appreciate irony and fun! :)

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

Re: Crashes When Printing

[JD]

Sandy Pamin wrote:

JD wrote:

Sandy Pamin wrote:

Seamonkey 2.0.14 has been crashing a lot lately when trying to print. I
get the Mozilla Crash Reporter. I happens with all 4 of my PC's, both
Win XP and Win 7. Pages print fine with IE. Any ideas?


about:crashes

Copy and paste one report in your reply so somebody can take a look at
what it says.

What kind of printer(s) and your printer(s) set-up?



Printer is Canon MX870, using a wireless network.


ID: d07f1d26-9787-4ff2-9637-a2d9f201
Signature: F_1359172165

* Details
* Modules
* Raw Dump
* Extensions
* Comments
* Correlations

Signature F_1359172165
UUID d07f1d26-9787-4ff2-9637-a2d9f201
Date Processed 2011-11-01 19:12:51.318680
Uptime 2455
Last Crash 41.0 minutes before submission
Install Age 6.1 weeks since version was first installed.
Install Time 2011-09-20 17:24:52
Product SeaMonkey
Version 2.0.14
Build ID 20110420224920
Release Channel unknown
OS Windows NT
OS Version 5.1.2600 Service Pack 3
CPU x86
CPU Info GenuineIntel family 15 model 4 stepping 1
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
Crash Address 0x0
User Comments
Processor Notes
EMCheckCompatibility False
Winsock LSP
Adapter Vendor ID
Adapter Device ID
Bugzilla - Report this Crash
Crashing Thread
Frame Module Signature [Expand] Source
0 NPSWF32.dll F_1359172165
F_1929819672___:4795

1 NPSWF32.dll NPP_Print
F271887804___:1760

2 seamonkey.exe nsNPAPIPluginInstance::Print
modules/plugin/base/src/nsNPAPIPluginInstance.cpp:1165
3 seamonkey.exe nsObjectFrame::PrintPlugin
layout/generic/nsObjectFrame.cpp:1310
4 seamonkey.exe nsObjectFrame::PaintPrintPlugin
layout/generic/nsObjectFrame.cpp:1117
5 seamonkey.exe nsDisplayGeneric::Paint layout/base/nsDisplayList.h:875
6 seamonkey.exe nsDisplayList::Paint layout/base/nsDisplayList.cpp:313
7 seamonkey.exe nsLayoutUtils::PaintFrame
layout/base/nsLayoutUtils.cpp:1114
8 seamonkey.exe nsPageFrame::PaintPageContent
layout/generic/nsPageFrame.cpp:582
9 seamonkey.exe PaintPageContent layout/generic/nsPageFrame.cpp:405
10 seamonkey.exe nsDisplayGeneric::Paint layout/base/nsDisplayList.h:875
11 seamonkey.exe nsDisplayList::Paint layout/base/nsDisplayList.cpp:313
12 seamonkey.exe nsLayoutUtils::PaintFrame
layout/base/nsLayoutUtils.cpp:1114
13 seamonkey.exe nsSimplePageSequenceFrame::PrintNextPage
layout/generic/nsSimplePageSequence.cpp:648
14 seamonkey.exe nsPrintEngine::PrintPage
layout/printing/nsPrintEngine.cpp:2431
15 seamonkey.exe nsPagePrintTimer::Notify
layout/printing/nsPagePrintTimer.cpp:90
16 xpcom_core.dll nsTimerImpl::Fire xpcom/threads/nsTimerImpl.cpp:423
17 xpcom_core.dll nsTimerEvent::Run xpcom/threads/nsTimerImpl.cpp:512
18 xpcom_core.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:521
19 xpcom_core.dll NS_ProcessNextEvent_P
objdir/mozilla/xpcom/build/nsThreadUtils.cpp:247
20 seamonkey.exe nsBaseAppShell::Run
widget/src/xpwidgets/nsBaseAppShell.cpp:170
21 seamonkey.exe nsAppStartup::Run
toolkit/components/startup/src/nsAppStartup.cpp:193
22 seamonkey.exe XRE_main toolkit/xre/nsAppRunner.cpp:3321
23 seamonkey.exe NS_internal_main suite/app/nsSuiteApp.cpp:103
24 seamonkey.exe wmain toolkit/xre/nsWindowsWMain.cpp:110
25 seamonkey.exe __tmainCRTStartup
objdir/mozilla/memory/jemalloc/src/crtexe.c:591
26 kernel32.dll BaseProcessStart


I see this:

Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ

I can't find an explanation as to what it means.

Any reason you've stuck with SM 2.0.14? The latest version is 2.4.1.

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

Re: Crashes When Printing

[JD]

Sandy Pamin wrote:

Seamonkey 2.0.14 has been crashing a lot lately when trying to print. I
get the Mozilla Crash Reporter. I happens with all 4 of my PC's, both
Win XP and Win 7. Pages print fine with IE. Any ideas?


about:crashes

Copy and paste one report in your reply so somebody can take a look at 
what it says.


What kind of printer(s) and your printer(s) set-up?

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

Re: Crashes When Printing

[Sandy Pamin]

JD wrote:

Sandy Pamin wrote:

Seamonkey 2.0.14 has been crashing a lot lately when trying to print. I
get the Mozilla Crash Reporter. I happens with all 4 of my PC's, both
Win XP and Win 7. Pages print fine with IE. Any ideas?


about:crashes

Copy and paste one report in your reply so somebody can take a look at
what it says.

What kind of printer(s) and your printer(s) set-up?



Printer is Canon MX870, using a wireless network.


ID: d07f1d26-9787-4ff2-9637-a2d9f201
Signature: F_1359172165

* Details
* Modules
* Raw Dump
* Extensions
* Comments
* Correlations

Signature   F_1359172165
UUIDd07f1d26-9787-4ff2-9637-a2d9f201
Date Processed  2011-11-01 19:12:51.318680
Uptime  2455
Last Crash  41.0 minutes before submission
Install Age 6.1 weeks since version was first installed.
Install Time2011-09-20 17:24:52
Product SeaMonkey
Version 2.0.14
Build ID20110420224920
Release Channel unknown
OS  Windows NT
OS Version  5.1.2600 Service Pack 3
CPU x86
CPU InfoGenuineIntel family 15 model 4 stepping 1
Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0x0
User Comments   
Processor Notes 
EMCheckCompatibilityFalse
Winsock LSP 
Adapter Vendor ID   
Adapter Device ID   
Bugzilla - Report this Crash
Crashing Thread
Frame   Module  Signature [Expand]  Source
0 	NPSWF32.dll 	F_1359172165 
F_1929819672___:4795
1 	NPSWF32.dll 	NPP_Print 
F271887804___:1760
2 	seamonkey.exe 	nsNPAPIPluginInstance::Print 
modules/plugin/base/src/nsNPAPIPluginInstance.cpp:1165
3 	seamonkey.exe 	nsObjectFrame::PrintPlugin 
layout/generic/nsObjectFrame.cpp:1310
4 	seamonkey.exe 	nsObjectFrame::PaintPrintPlugin 
layout/generic/nsObjectFrame.cpp:1117

5   seamonkey.exe   nsDisplayGeneric::Paint 
layout/base/nsDisplayList.h:875
6   seamonkey.exe   nsDisplayList::Paint
layout/base/nsDisplayList.cpp:313
7 	seamonkey.exe 	nsLayoutUtils::PaintFrame 
layout/base/nsLayoutUtils.cpp:1114
8 	seamonkey.exe 	nsPageFrame::PaintPageContent 
layout/generic/nsPageFrame.cpp:582

9   seamonkey.exe   PaintPageContent
layout/generic/nsPageFrame.cpp:405
10  seamonkey.exe   nsDisplayGeneric::Paint 
layout/base/nsDisplayList.h:875
11  seamonkey.exe   nsDisplayList::Paint
layout/base/nsDisplayList.cpp:313
12 	seamonkey.exe 	nsLayoutUtils::PaintFrame 
layout/base/nsLayoutUtils.cpp:1114
13 	seamonkey.exe 	nsSimplePageSequenceFrame::PrintNextPage 
layout/generic/nsSimplePageSequence.cpp:648
14 	seamonkey.exe 	nsPrintEngine::PrintPage 
layout/printing/nsPrintEngine.cpp:2431
15 	seamonkey.exe 	nsPagePrintTimer::Notify 
layout/printing/nsPagePrintTimer.cpp:90

16  xpcom_core.dll  nsTimerImpl::Fire   
xpcom/threads/nsTimerImpl.cpp:423
17  xpcom_core.dll  nsTimerEvent::Run   
xpcom/threads/nsTimerImpl.cpp:512
18 	xpcom_core.dll 	nsThread::ProcessNextEvent 
xpcom/threads/nsThread.cpp:521
19 	xpcom_core.dll 	NS_ProcessNextEvent_P 
objdir/mozilla/xpcom/build/nsThreadUtils.cpp:247
20 	seamonkey.exe 	nsBaseAppShell::Run 
widget/src/xpwidgets/nsBaseAppShell.cpp:170
21 	seamonkey.exe 	nsAppStartup::Run 
toolkit/components/startup/src/nsAppStartup.cpp:193

22  seamonkey.exe   XRE_maintoolkit/xre/nsAppRunner.cpp:3321
23  seamonkey.exe   NS_internal_mainsuite/app/nsSuiteApp.cpp:103
24  seamonkey.exe   wmain   toolkit/xre/nsWindowsWMain.cpp:110
25 	seamonkey.exe 	__tmainCRTStartup 
objdir/mozilla/memory/jemalloc/src/crtexe.c:591

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

Re: crashes in flash

[cyberzen]

cyberzen a écrit :

cyberzen a écrit :

ID: 6a55d3c8-0813-44b2-a12a-331d52110323
Signature: F1292875159_

with flashblock on I have one per day approx

SM 2.0.13 will not solve this I suppose..


that did not..
but..
as I found a site

http://www.classicalarchives.com/

where I had a crash every time I wanted to play the
free 1-click concert
I tried to uninstall the most recent extension I made : prefbar
bingo
this is working again...

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

Re: crashes in flash

[David E. Ross]

On 3/25/11 1:15 AM, cyberzen wrote:
 cyberzen a écrit :
 cyberzen a écrit :
 ID: 6a55d3c8-0813-44b2-a12a-331d52110323
 Signature: F1292875159_

 with flashblock on I have one per day approx
 SM 2.0.13 will not solve this I suppose..

 that did not..
 but..
 as I found a site
 
 http://www.classicalarchives.com/
 
 where I had a crash every time I wanted to play the
 free 1-click concert
 I tried to uninstall the most recent extension I made : prefbar
 bingo
 this is working again...
 

I tried that site.  It told me that it wanted popups unblocked, so I
unblocked them.  It did not tell me that it wanted Flash enabled, but I
guessed that I should enable it.  Then, everything worked okay.  This
was with PrefBar 5.1.1 installed.

Rather than using an external audio application (e.g., RealPlayer,
WinAmp, Windows Media Player, iTunes), the page uses Flash to play
streaming music.  Note that the PrefBar capability to disable Flash is
often problematical.  Thus, I installed FlashBlock and then created a
PrefBar checkbox that enables or disables FlashBlock.  I have had no
problems with this configuration.

-- 

David E. Ross
http://www.rossde.com/

On occasion, I might filter and ignore all newsgroup messages
posted through GoogleGroups via Google's G2/1.0 user agent
because of spam from that source.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: crashes in flash

[cyberzen]

David E. Ross a écrit :

On 3/25/11 1:15 AM, cyberzen wrote:

cyberzen a écrit :

cyberzen a écrit :

ID: 6a55d3c8-0813-44b2-a12a-331d52110323
Signature: F1292875159_

with flashblock on I have one per day approx

SM 2.0.13 will not solve this I suppose..


that did not..
but..
as I found a site

http://www.classicalarchives.com/

where I had a crash every time I wanted to play the
free 1-click concert
I tried to uninstall the most recent extension I made : prefbar
bingo
this is working again...



I tried that site.  It told me that it wanted popups unblocked, so I
unblocked them.  It did not tell me that it wanted Flash enabled, but I
guessed that I should enable it.  Then, everything worked okay.  This
was with PrefBar 5.1.1 installed.

Rather than using an external audio application (e.g., RealPlayer,
WinAmp, Windows Media Player, iTunes), the page uses Flash to play
streaming music.  Note that the PrefBar capability to disable Flash is
often problematical.  Thus, I installed FlashBlock and then created a
PrefBar checkbox that enables or disables FlashBlock.  I have had no
problems with this configuration.


maybe you can have prefbar on your side with no problems

in fact I don't think prefbar is the real culprit in this case, removing 
it just modified the memory layout, and thus avoiding

Crash ReasonEXCEPTION_ACCESS_VIOLATION_READ
Crash Address   0xc9fc050

I have no proof that flash is the bad guy, but it could make a good 
suspect at least




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

Re: crashes in flash

[cyberzen]

cyberzen a écrit :

ID: 6a55d3c8-0813-44b2-a12a-331d52110323
Signature: F1292875159_

with flashblock on I have one per day approx

SM 2.0.13 will not solve this I suppose..

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

Re: crashes in flash

[David E. Ross]

On 3/23/11 1:44 AM, cyberzen wrote:
 ID: 6a55d3c8-0813-44b2-a12a-331d52110323
 Signature: F1292875159_
 
 with flashblock on I have one per day approx

I have not seen this problem.  Is it possible you have a bad
installation of Flash?  The NPSWF32.dll plugin does NOT go in the
SeaMonkey plugins folder.  It goes where the installer executable places
it, in C:\WINDOWS\system32\Macromed\Flash\.

-- 

David E. Ross
http://www.rossde.com/

On occasion, I might filter and ignore all newsgroup messages
posted through GoogleGroups via Google's G2/1.0 user agent
because of spam from that source.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: crashes in flash

[cyberzen]

David E. Ross a écrit :

On 3/23/11 1:44 AM, cyberzen wrote:

ID: 6a55d3c8-0813-44b2-a12a-331d52110323
Signature: F1292875159_

with flashblock on I have one per day approx


I have not seen this problem.  Is it possible you have a bad
installation of Flash?  The NPSWF32.dll plugin does NOT go in the
SeaMonkey plugins folder.  It goes where the installer executable places
it, inC:\WINDOWS\system32\Macromed\Flash\.


I checked this point
no problem
when I began to have the crashes, I reinstalled the new fresh release of 
flash

have a view on the end of FlashInstall.log

=O== M/10.2.152.26 2011-03-02+18-46-41.232 
 [I] 0010 
C:\WINDOWS\system32\Macromed\Flash\FlashUtil10m_Plugin.exe -update plugin

0001 [I] 0011 0
=X== M/10.2.152.26 2011-03-02+18-46-59.326 

=O== M/10.2.152.32 2011-03-02+18-47-02.810 
 [I] 0010 
C:\DOCUME~1\\LOCALS~1\Temp\7.dir\InstallFlashPlayer.exe -iv 0

0001 [W] 1036 Software\Mozilla\Firefox\extensions/Plugins 2
0002 [W] 1036 Software\Mozilla\Mozilla Firefox\extensions/Plugins 2
0003 [W] 1036 Software\Mozilla\SeaMonkey\extensions/Plugins 2
0004 [W] 1036 Software\Opera Software/Last CommandLine 2
0005 [W] 1036 Software\Opera Software/Last CommandLine 2
0006 [W] 1036 Software\Opera Software/Plugin Path 2
0007 [W] 1036 Software\Opera Software/Plugin Path 2
0008 [I] 0014 C:\WINDOWS\system32\Macromed\Flash\NPSWF32.dll
0009 [I] 0015 C:\WINDOWS\system32\Macromed\Flash\FlashUtil10n_Plugin.exe
0010 [I] 0017 C:\WINDOWS\system32\Macromed\Flash
=X== M/10.2.152.32 2011-03-02+18-47-55.699 

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

Re: Crashes after 2.0.7 update - possible fix

[Sebastian]

On 9 Sep., 02:16, Robert Kaiser ka...@kairo.at wrote:
 If you are seeing a crash (probably when profile manager should come up)
 after getting an update to 2.0.7, please try to go into the SeaMonkey
 application/install folder, find a subfolder named components and
 remove the compreg.dat file inside it.

 If that works, please tell us here so we can produce and deploy a 2.0.8
 as fast as possible to fix this for everyone!


HI Roland, thanks for quick help in Forum and working on Seamonkey all
the time!!
Yes, i had that problem, and your fix described above worked fine and
easy for me. (Being cautious with deleting files, i renamed
compreg.dat first instead of deleting it. However solution works as
well).

best regards.

Sebastian





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

Re: Crashes after 2.0.7 update - possible fix

[robert . gault]

Robert Kaiser wrote:

Hi,

If you are seeing a crash (probably when profile manager should come up)
after getting an update to 2.0.7, please try to go into the SeaMonkey
application/install folder, find a subfolder named components and
remove the compreg.dat file inside it.

If that works, please tell us here so we can produce and deploy a 2.0.8
as fast as possible to fix this for everyone!

Thanks and sorry for any problems,

Robert Kaiser



This crash occurs when trying to start profile manager but not when starting a 
profile with ex.

D:\Program Files\seamonkey2\seamonkey.exe -P Robert -browser

I was not aware there was a problem with 2.0.7 until reading these messages. The 
fix of deleting or renaming the .dat file does work.

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

Re: Crashes after 2.0.7 update - possible fix

[David E. Ross]

On 9/8/10 5:16 PM, Robert Kaiser wrote:
 Hi,
 
 If you are seeing a crash (probably when profile manager should come up) 
 after getting an update to 2.0.7, please try to go into the SeaMonkey 
 application/install folder, find a subfolder named components and 
 remove the compreg.dat file inside it.
 
 If that works, please tell us here so we can produce and deploy a 2.0.8 
 as fast as possible to fix this for everyone!
 
 Thanks and sorry for any problems,
 
 Robert Kaiser
 

I had 8 files named compreg.dat, one of which was in a folder named
components.

I saw the crash only if I launched the Profile Manager when SeaMonkey
was not already operating.  With compreg.dat deleted from components, I
don't see that crash anymore.

-- 

David E. Ross
http://www.rossde.com/

I am again filtering and ignoring all newsgroup messages posted
through GoogleGroups via Google's G2/1.0 user agent because of the
amount of spam from that source.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Crashes after 2.0.7 update - possible fix

[Robert Kaiser]

JOLAN1 schrieb:

On Sep 8, 6:16 pm, Robert Kaiserka...@kairo.at  wrote:

Hi,

If you are seeing a crash (probably when profile manager should come up)
after getting an update to 2.0.7, please try to go into the SeaMonkey
application/install folder, find a subfolder named components and
remove the compreg.dat file inside it.


OK!  That worksBUT...I wouldn't have been able to read your 'fix'
if I hadn't had the forsight to leave SeaMonkey 1.1.18 still installed
( 2.06 installed on another partition)!  So, I don't think many with
this problem  will read your suggestion.


That's why we stopped delivering updates to 2.0.6 users when we noticed 
this problem.
We unfortunately can't do much other then informing those who already 
have the 2.0.7 update, as the application would need to successfully 
start up so we can deliver another update that cares about cleaning 
compreg.dat. We need to reach those people to either go in and clean 
that file theirselves or clean the whole SeaMonkey folder and reinstall 
2.0.7 (as then it works fine).


Knowing that deleting this file helps is good so we can roll out a 2.0.8 
version (just to avoid confusion) that actually is the same as 2.0.7 but 
deletes this files on update or install if it does exist.



While I'm at it, I continue to have password problems, not with the
master password but when it comes to filling in username  password
for my various accounts... 2.xx does not fill in the blanks like the
1.xx series did.  Consequently, my secretaries are always
'guessing'.   Total waste of time.  Can't that be fixed ???


Please ask the support group for that, there are several possible 
causes. For one thing, try to double-click the user fields and see if 
user names are suggested in a dropdown then.


Thanks for the report,

Robert Kaiser

--
Note that any statements of mine - no matter how passionate - are never 
meant to be offensive but very often as food for thought or possible 
arguments that we as a community needs answers to. And most of the time, 
I even appreciate irony and fun! :)

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

Re: Crashes after 2.0.7 update - possible fix

[David Wilkinson]

Robert Kaiser wrote:

JOLAN1 schrieb:

On Sep 8, 6:16 pm, Robert Kaiserka...@kairo.at wrote:

Hi,

If you are seeing a crash (probably when profile manager should come up)
after getting an update to 2.0.7, please try to go into the SeaMonkey
application/install folder, find a subfolder named components and
remove the compreg.dat file inside it.


Can/should we delete that file before doing the 2.0.7 update? My computer has 
downloaded the update, but hasn't installed it yet.


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

Re: Crashes after 2.0.7 update - possible fix

[Robert Kaiser]

David Wilkinson schrieb:

Robert Kaiser wrote:

JOLAN1 schrieb:

On Sep 8, 6:16 pm, Robert Kaiserka...@kairo.at wrote:

Hi,

If you are seeing a crash (probably when profile manager should come
up)
after getting an update to 2.0.7, please try to go into the SeaMonkey
application/install folder, find a subfolder named components and
remove the compreg.dat file inside it.


Can/should we delete that file before doing the 2.0.7 update? My
computer has downloaded the update, but hasn't installed it yet.


As long as you don't crash on launching the profile manager, it doesn't 
matter if you delete it or not, but you can always do it as it will be 
regenerated anyhow.


Robert Kaiser


--
Note that any statements of mine - no matter how passionate - are never 
meant to be offensive but very often as food for thought or possible 
arguments that we as a community needs answers to. And most of the time, 
I even appreciate irony and fun! :)

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