Re: Seamonkey Mail crashes at opening

[Dirk Fieldhouse]

On 01/11/19 02:06, BigBlue wrote:

The Ultramon developer got back to me and said v3.4.1 should be fine with the 
latest Seamonkey and Windows 10. I did download it and try and Seamonkey Mail 
does start OK after that, but haven't tested extensively. Looks good.


Great. A Windows 10 update was the breaking change, judging from the 
UltraMon release notes. Perhaps there was a bug in the way that UltraMon 
interacted with Windows, only revealed by a newer version of Windows, or 
perhaps Microsoft changed something behind the scenes.


/df

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

Re: Seamonkey Mail crashes at opening

[BigBlue]

The Ultramon developer got back to me and said v3.4.1 should be fine with the 
latest Seamonkey and Windows 10. I did download it and try and Seamonkey Mail 
does start OK after that, but haven't tested extensively. Looks good. 
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[BigBlue]

On Thursday, October 31, 2019 at 6:50:36 PM UTC-5, nor...@googlegroups.com 
wrote:
> On 31/10/19 14:53, BigBlue wrote:
> > ... Looks like something about UltraMon became incompatible with SeaMonkey 
> > Mail. I can certainly live without UltraMon for a while - more easily than 
> > living without Mail. I'll report a bug to them and see if they can fix 
> > things.
> 
> The product site says that you need v3.4.1 x64 
>  if your 
> W10 is 1809 or later, and W10 >= 1607 in any case. Apparently they broke 
> Chrome as well.
> 
> Having said that, it had better be pretty good at $40 a time. For 
> someone who hadn't already bought a licence, this 
>  or just the built-in W10 
> multi-monitor settings, might be enough.
> 
> /df
> 
> -- 
> London
> UK

It wasn't $40 when I bought it. I've been using it for maybe 10 years. Not sure 
which version I had, but I do still have a 3.4.0 download so that's probably 
the one. I can try 3.4.1 and see if that helps. Interestingly, Ultramon didn't 
break things though. My Seamonkey Mail worked fine for years with it. Something 
changed in Seamonkey and others like Mozilla and Chrome (or maybe Windows 
itself) that broke things. Definitely up to Ultramon to resolve though.

The good thing about Ultramon was the additional buttons it adds to windows to 
allow you to instantly move them over to the other monitor without having to 
drag across, plus the ability to maximize a window across both monitors. And 
other semi-minor tweaks.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[Dirk Fieldhouse]

On 31/10/19 14:53, BigBlue wrote:

... Looks like something about UltraMon became incompatible with SeaMonkey 
Mail. I can certainly live without UltraMon for a while - more easily than 
living without Mail. I'll report a bug to them and see if they can fix things.


The product site says that you need v3.4.1 x64 
 if your 
W10 is 1809 or later, and W10 >= 1607 in any case. Apparently they broke 
Chrome as well.


Having said that, it had better be pretty good at $40 a time. For 
someone who hadn't already bought a licence, this 
 or just the built-in W10 
multi-monitor settings, might be enough.


/df

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

Re: Seamonkey Mail crashes at opening

[BigBlue]

On Thursday, October 31, 2019 at 10:16:02 AM UTC-5, Frank-Rainer Grahl wrote:
> BigBlue wrote:
> > That's it! Thanks for pointing me to the crash report. I had no idea that 
> > existed. The crash report indicated the failure was with 
> > rtsultramonhookx32.dll. That sounded familiar so I checked and it is 
> > related to multi-monitor software I had installed called UltraMon (which 
> > has always been a very useful tool for me, but I don't use its features as 
> > much as I used to). To check the relationship, I uninstalled it and now I 
> > can launch Mail without any issue. Looks like something about UltraMon 
> > became incompatible with SeaMonkey Mail. I can certainly live without 
> > UltraMon for a while - more easily than living without Mail. I'll report a 
> > bug to them and see if they can fix things.
> > 
> > Thanks a ton!!
> > 
> 
> Just searching for it shows similar reports for Firefox and other software:
> 
> https://crash-stats.mozilla.com/report/index/d49d0f06-2e09-44bb-88d5-d97bf0181227#tab-details
> 
> This needs to be fixed in ultramon.
> 
> FRG


Yep. I contacted RealTimeSoft and let them know. Not sure if they still support 
UltraMon. Last release was Oct 4, 2018.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[Frank-Rainer Grahl]

budkrueg...@gmail.com wrote:

On Wednesday, October 30, 2019 at 10:16:24 PM UTC-4, BigBlue wrote:

[Seamonkey 2.49.5 on Windows 10 (up to date)]

Since I did a full uninstall/reinstall and did not add any themes or add-ons I 
know those are not the issue. So what else is it about safe mode that could 
allow mail to start when all of the other things are ruled out?

Thanks!


I'm getting worried. I still have 2.49.4 and it is working fine.  These recent 
threads about serious problems with any version after 2.49.4 has me leery of 
updating to 2.49.5.  These threads tell me that you folks are obviously out of 
my league of expertise. Is it safe for me to go to 2.49.5?  TIA.  Bud Krueger



We monitored the crash stats after release and there is nothing which stands 
out. I ran 2.49.5 for at least a year before switiching to 2.53.
One of the  problems is that recent third party antivirus release become more 
and more a virus itself. Windows 10 updates are not always stable too. Linux 
becomes more fragmented every year and macOS stability isn't that great either 
any longer. If 2.49.5 does not work for you you can always reinstall 2.49.4 again.


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

Re: Seamonkey Mail crashes at opening

[Frank-Rainer Grahl]

BigBlue wrote:

That's it! Thanks for pointing me to the crash report. I had no idea that 
existed. The crash report indicated the failure was with 
rtsultramonhookx32.dll. That sounded familiar so I checked and it is related to 
multi-monitor software I had installed called UltraMon (which has always been a 
very useful tool for me, but I don't use its features as much as I used to). To 
check the relationship, I uninstalled it and now I can launch Mail without any 
issue. Looks like something about UltraMon became incompatible with SeaMonkey 
Mail. I can certainly live without UltraMon for a while - more easily than 
living without Mail. I'll report a bug to them and see if they can fix things.

Thanks a ton!!



Just searching for it shows similar reports for Firefox and other software:

https://crash-stats.mozilla.com/report/index/d49d0f06-2e09-44bb-88d5-d97bf0181227#tab-details

This needs to be fixed in ultramon.

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

Re: Seamonkey Mail crashes at opening

[BigBlue]

That's it! Thanks for pointing me to the crash report. I had no idea that 
existed. The crash report indicated the failure was with 
rtsultramonhookx32.dll. That sounded familiar so I checked and it is related to 
multi-monitor software I had installed called UltraMon (which has always been a 
very useful tool for me, but I don't use its features as much as I used to). To 
check the relationship, I uninstalled it and now I can launch Mail without any 
issue. Looks like something about UltraMon became incompatible with SeaMonkey 
Mail. I can certainly live without UltraMon for a while - more easily than 
living without Mail. I'll report a bug to them and see if they can fix things.

Thanks a ton!!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[BigBlue]

On Thursday, October 31, 2019 at 9:10:46 AM UTC-5, WaltS48 wrote:
> On 10/31/19 8:49 AM, BigBlue wrote:
> > On Thursday, October 31, 2019 at 5:39:27 AM UTC-5, Frank-Rainer Grahl wrote:
> >> BigBlue wrote:
> >>> [Seamonkey 2.49.5 on Windows 10 (up to date)]
> >>>
> >>
> >>> Since I did a full uninstall/reinstall and did not add any themes or 
> >>> add-ons I know those are not the issue. So what else is it about safe 
> >>> mode that could allow mail to start when all of the other things are 
> >>> ruled out?
> >>>
> >>> Thanks!
> >>>
> >>
> >> Video driver antivirus? Best to post a crash id.
> >>
> >> FRG
> > 
> > I have active AV and I did run MalwareBytes to double-check. What does it 
> > mean to post a crash id?
> > 
> 
> It means you type about:crashes into the address bar, then copy the most 
> recent link and post it into a reply.
> 
> -- 
> OS: Ubuntu Linux 18.04LTS - Gnome Desktop
> https://www.thunderbird.net/en-US/get-involved/


Gotcha. Here's one I just created:
bp-b68ef33c-85b1-476d-a74d-0fc860191031

http://crash-stats.mozilla.com/report/index/bp-b68ef33c-85b1-476d-a74d-0fc860191031

As for trying 32-bit vs. 64 bit, I haven't done that. I suppose I can give it a 
try.

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

Re: Seamonkey Mail crashes at opening

[budkrueger3]

On Wednesday, October 30, 2019 at 10:16:24 PM UTC-4, BigBlue wrote:
> [Seamonkey 2.49.5 on Windows 10 (up to date)]
> 
> I've used Seamonkey for many years, mainly for the Mail client. Love it. For 
> the past couple of months I've had problems when starting Mail (using 
> v2.49.2) where it would crash almost immediately after opening. It would, 
> however, instantiate the Mail window for a second or so, and sometimes if I 
> clicked into a folder in one of my mail accounts in that initial second it 
> would just work normally. Usually took me 4-6 startup attempts to get it to 
> stay running. Once running it was mostly solid for until I rebooted or exited 
> Mail. Nothing else was affected. I could run Browser, Address Book, Composer 
> just fine all the time.
> 
> Yesterday I realized that Seamonkey was no longer auto-updating so I updated 
> manually to 2.49.5 (latest). With this version the crashes still happen but 
> are now immediate after launching it (either directly via the -mail flag or 
> by clicking the envelope icon in Browser). It doesn't launch the window at 
> all now so my trick above is useless.
> 
> I tried all the usual troubleshooting steps:
> 
>  - Start with a new profile. With a new profile it will run Mail one time, 
> but on the next launch it goes back to crashing. This is regardless of 
> whether I set up a mail account or not. 
>  - Clean install, by doing full uninstall and removing the 
> C:\Users\myuser\AppData\Local\Mozilla\Seamonkey\Profiles\ folder 
> entirely. Same as above.
>  - Run Windows in safe mode. Same result.
>  - Revert back to 2.49.2. Same result.
>  - Disable hardware acceleration. Same.
>  - Disable my antivirus software. Same.
>  
> Bear in mind that at this point I have zero mail accounts set up and am 
> totally default on all Seamonkey settings, with nothing added or changed. The 
> only way I can get it to work now is by starting Seamonkey in safe mode. When 
> I do that it works fine. But obviously this is not ideal, especially since it 
> won't save any UI changes between sessions (reordering columns, expanding 
> e-mail account trees, etc.). I have configured my mail accounts while in 
> Seamonkey safe mode and things work great between starts as long as I use 
> safe mode every time. It is just the lack of control on the above that I 
> don't like. I suppose I could just always run it in safe mode and get used to 
> the lack of ability to change things, but I'm bothered by the whole situation.
> 
> Since I did a full uninstall/reinstall and did not add any themes or add-ons 
> I know those are not the issue. So what else is it about safe mode that could 
> allow mail to start when all of the other things are ruled out?
> 
> Thanks!

I'm getting worried. I still have 2.49.4 and it is working fine.  These recent 
threads about serious problems with any version after 2.49.4 has me leery of 
updating to 2.49.5.  These threads tell me that you folks are obviously out of 
my league of expertise. Is it safe for me to go to 2.49.5?  TIA.  Bud Krueger
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[WaltS48]

On 10/31/19 8:49 AM, BigBlue wrote:

On Thursday, October 31, 2019 at 5:39:27 AM UTC-5, Frank-Rainer Grahl wrote:

BigBlue wrote:

[Seamonkey 2.49.5 on Windows 10 (up to date)]




Since I did a full uninstall/reinstall and did not add any themes or add-ons I 
know those are not the issue. So what else is it about safe mode that could 
allow mail to start when all of the other things are ruled out?

Thanks!



Video driver antivirus? Best to post a crash id.

FRG


I have active AV and I did run MalwareBytes to double-check. What does it mean 
to post a crash id?



It means you type about:crashes into the address bar, then copy the most 
recent link and post it into a reply.


--
OS: Ubuntu Linux 18.04LTS - Gnome Desktop
https://www.thunderbird.net/en-US/get-involved/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[Dirk Fieldhouse]

On 31/10/19 12:56, BigBlue wrote:


... >

...I don't know exactly what the two *.css files do, but I'd assume on a fresh install with stock/default new profile they would be irrelevant. 


Override styles of the application (userChrome) or web pages 
(userContent), and yes.



I couldn't find 
any way to make a change to Java outside of safe mode, but with a fresh install 
and zero accounts/content would that matter?


Once you could disable the JS JIT compiler by making both these boolean 
settings false in about:config: javascript.options.jit.content and 
javascript.options.jit.chrome. But this is also likely to be irrelevant.


The PC is otherwise well cared for and healthy. It is 64-bit Windows 10 Home on 
32GB memory system that is 1 year old. Always had AV. Fully up-to-date on 
Windows updates. Disk is SSD and has shown no indications of issues. I suppose 
I can force a ckddsk just in case.


You could.

Is SM 64- or 32-bit? What happens if you try the other bit-ness?

And as frg says, a crash ID would help (about:crashes).

/df

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

Re: Seamonkey Mail crashes at opening

[BigBlue]

On Thursday, October 31, 2019 at 7:07:12 AM UTC-5, nor...@googlegroups.com 
wrote:

> It works with safe mode.
> 
> "Safe Mode temporarily affects the following:
> 
>  All extensions are disabled.
>  The default theme is used, without a persona.
>  The Just-in-time (JIT) JavaScript compiler is disabled.
>  The userChrome.css and userContent.css files are ignored.
>  The default toolbar layout is used.
>  Hardware acceleration is disabled.
> "
> 
> It crashes with a default profile on the second (and subsequent) run.
> 
> Therefore there is some problem with the way the profile is saved and 
> reloaded, that only seems to affect your system and SM installation.
> 
> How is disk health in this PC?
> 
> Has Windows 10 been updated recently? x64/x86?
> 

So I was going through that list before I originally posted. It seems like with 
a fresh install almost everything is rules out between safe mode and a normal 
run with default settings (theme, addons, toolbar layout) and I did explicitly 
try disabling hardware acceleration, which made no difference. I don't know 
exactly what the two *.css files do, but I'd assume on a fresh install with 
stock/default new profile they would be irrelevant. I couldn't find any way to 
make a change to Java outside of safe mode, but with a fresh install and zero 
accounts/content would that matter?

The PC is otherwise well cared for and healthy. It is 64-bit Windows 10 Home on 
32GB memory system that is 1 year old. Always had AV. Fully up-to-date on 
Windows updates. Disk is SSD and has shown no indications of issues. I suppose 
I can force a ckddsk just in case.

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

Re: Seamonkey Mail crashes at opening

[BigBlue]

On Thursday, October 31, 2019 at 5:39:27 AM UTC-5, Frank-Rainer Grahl wrote:
> BigBlue wrote:
> > [Seamonkey 2.49.5 on Windows 10 (up to date)]
> > 
> 
> > Since I did a full uninstall/reinstall and did not add any themes or 
> > add-ons I know those are not the issue. So what else is it about safe mode 
> > that could allow mail to start when all of the other things are ruled out?
> > 
> > Thanks!
> > 
> 
> Video driver antivirus? Best to post a crash id.
> 
> FRG

I have active AV and I did run MalwareBytes to double-check. What does it mean 
to post a crash id?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Seamonkey Mail crashes at opening

[Dirk Fieldhouse]

On 31/10/19 02:16, BigBlue wrote:

[Seamonkey 2.49.5 on Windows 10 (up to date)]

... With this version the crashes still happen but are now immediate after 
launching it (either directly via the -mail flag or by clicking the envelope 
icon in Browser). ...

I tried all the usual troubleshooting steps:

  - Start with a new profile. With a new profile it will run Mail one time, but 
on the next launch it goes back to crashing. This is regardless of whether I 
set up a mail account or not.
  - Clean install, by doing full uninstall and removing the 
C:\Users\myuser\AppData\Local\Mozilla\Seamonkey\Profiles\ folder 
entirely. Same as above.
  - Run Windows in safe mode. Same result.
  - Revert back to 2.49.2. Same result.
  - Disable hardware acceleration. Same.
  - Disable my antivirus software. Same.
  
Bear in mind that at this point I have zero mail accounts set up and am totally default on all Seamonkey settings, with nothing added or changed. The only way I can get it to work now is by starting Seamonkey in safe mode. When I do that it works fine.  > ... So what else is it about safe mode that could allow mail to start 

when all of the other things are ruled out?

It works with safe mode.

"Safe Mode temporarily affects the following:

All extensions are disabled.
The default theme is used, without a persona.
The Just-in-time (JIT) JavaScript compiler is disabled.
The userChrome.css and userContent.css files are ignored.
The default toolbar layout is used.
Hardware acceleration is disabled.
"

It crashes with a default profile on the second (and subsequent) run.

Therefore there is some problem with the way the profile is saved and 
reloaded, that only seems to affect your system and SM installation.


How is disk health in this PC?

Has Windows 10 been updated recently? x64/x86?

/df

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

Re: Seamonkey Mail crashes at opening

[Frank-Rainer Grahl]

BigBlue wrote:

[Seamonkey 2.49.5 on Windows 10 (up to date)]




Since I did a full uninstall/reinstall and did not add any themes or add-ons I 
know those are not the issue. So what else is it about safe mode that could 
allow mail to start when all of the other things are ruled out?

Thanks!



Video driver antivirus? Best to post a crash id.

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

Seamonkey Mail crashes at opening

[BigBlue]

[Seamonkey 2.49.5 on Windows 10 (up to date)]

I've used Seamonkey for many years, mainly for the Mail client. Love it. For 
the past couple of months I've had problems when starting Mail (using v2.49.2) 
where it would crash almost immediately after opening. It would, however, 
instantiate the Mail window for a second or so, and sometimes if I clicked into 
a folder in one of my mail accounts in that initial second it would just work 
normally. Usually took me 4-6 startup attempts to get it to stay running. Once 
running it was mostly solid for until I rebooted or exited Mail. Nothing else 
was affected. I could run Browser, Address Book, Composer just fine all the 
time.

Yesterday I realized that Seamonkey was no longer auto-updating so I updated 
manually to 2.49.5 (latest). With this version the crashes still happen but are 
now immediate after launching it (either directly via the -mail flag or by 
clicking the envelope icon in Browser). It doesn't launch the window at all now 
so my trick above is useless.

I tried all the usual troubleshooting steps:

 - Start with a new profile. With a new profile it will run Mail one time, but 
on the next launch it goes back to crashing. This is regardless of whether I 
set up a mail account or not. 
 - Clean install, by doing full uninstall and removing the 
C:\Users\myuser\AppData\Local\Mozilla\Seamonkey\Profiles\ folder 
entirely. Same as above.
 - Run Windows in safe mode. Same result.
 - Revert back to 2.49.2. Same result.
 - Disable hardware acceleration. Same.
 - Disable my antivirus software. Same.
 
Bear in mind that at this point I have zero mail accounts set up and am totally 
default on all Seamonkey settings, with nothing added or changed. The only way 
I can get it to work now is by starting Seamonkey in safe mode. When I do that 
it works fine. But obviously this is not ideal, especially since it won't save 
any UI changes between sessions (reordering columns, expanding e-mail account 
trees, etc.). I have configured my mail accounts while in Seamonkey safe mode 
and things work great between starts as long as I use safe mode every time. It 
is just the lack of control on the above that I don't like. I suppose I could 
just always run it in safe mode and get used to the lack of ability to change 
things, but I'm bothered by the whole situation.

Since I did a full uninstall/reinstall and did not add any themes or add-ons I 
know those are not the issue. So what else is it about safe mode that could 
allow mail to start when all of the other things are ruled out?

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

Re: Suddenly frequent SM crashes

[chokito]

Or use WG9s SeaMonkey version 2.49.5 from Bill Gianopoulos at 
https://www.wg9s.com/comm-esr/.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Suddenly frequent SM crashes

[Frank-Rainer Grahl]

Ken Rudolph wrote:
SeaMonkey has crashed 3 times in the past 3 hours and once last night. I've 
gone several months without crashes; so this cluster comes out of the blue.


Win 10.0 17134
SM 2.49.1esr

Each has the same crash reason:  EXCEPTION_ACCESS_VIOLATION_READ

There's lots more in the crash report that I think was automatically sent to 
Mozilla.  But I was wondering if anybody has an idea of what to do about this?


Latest version is 2.49.4. I would try this one first. Maybe a Windows 10 
update has changed something. If the crashes persist please post a crash id.


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

Re: Suddenly frequent SM crashes

[Don Spam's Reckless Son]

Ken Rudolph wrote:
SeaMonkey has crashed 3 times in the past 3 hours and once last night. 
I've gone several months without crashes; so this cluster comes out of 
the blue.


Win 10.0 17134
SM 2.49.1esr

Each has the same crash reason:  EXCEPTION_ACCESS_VIOLATION_READ

There's lots more in the crash report that I think was automatically 
sent to Mozilla.  But I was wondering if anybody has an idea of what to 
do about this?




2.49.4 is the current version and it has been around for a long time 
nowadays, auto-update does not work at present so you will have to 
download it from (for example) https://www.seamonkey-project.org/ and 
install it directly.  The release notes could tell you if some bug in 
your older level has since been fixed.



--
spammus ergo sum, viruses courtesy of https://www.nsa.gov/malware/
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: Suddenly frequent SM crashes

[Paul Bergsagel]

Ken Rudolph wrote:
SeaMonkey has crashed 3 times in the past 3 hours and once last night. 
I've gone several months without crashes; so this cluster comes out of 
the blue.


Win 10.0 17134
SM 2.49.1esr

Each has the same crash reason:  EXCEPTION_ACCESS_VIOLATION_READ

There's lots more in the crash report that I think was automatically 
sent to Mozilla.  But I was wondering if anybody has an idea of what to 
do about this?


If you haven't rebooted your computer in a while, then it is worth 
rebooting to see if it clears up the crashes.


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

Suddenly frequent SM crashes

[Ken Rudolph]

SeaMonkey has crashed 3 times in the past 3 hours and once last night. 
I've gone several months without crashes; so this cluster comes out of 
the blue.


Win 10.0 17134
SM 2.49.1esr

Each has the same crash reason:  EXCEPTION_ACCESS_VIOLATION_READ

There's lots more in the crash report that I think was automatically 
sent to Mozilla.  But I was wondering if anybody has an idea of what to 
do about this?


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

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?
>>>
>>> <https://crash-stats.mozilla.com/report/index/2ec4f1b0-e335-4e9c-9227-1527d0190120#tab-bugzilla>
>>>
>>>
>>
>> I don't know enough about reading the crash report to match it to any of
>> the bug reports.  I was just closing a SM tab when it occurred, but it
>> is certainly possible something was going on in another tab or in the
>> mail/news window when it happened.  I trust someone who can read the
>> report will be able to match it to one of them or open a new one if it
>> needs to be done.
>>
>> Dave
>>

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

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



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

Dave


___
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?
> 
> <https://crash-stats.mozilla.com/report/index/2ec4f1b0-e335-4e9c-9227-1527d0190120#tab-bugzilla>
> 

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

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

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

-- 

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

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

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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.













___
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 :
>>>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>

___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.










___
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 :
>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>

___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 












___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.










___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 











___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 










___
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 :
>>>>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>

___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>. 









___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.







___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.




___
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 :
<https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.



-- 

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 :
>> <https://crash-stats.mozilla.com/report/index/0048e3a0-7eb3-4ba1-89ec-36c510181231>.
>>
>>
>>
>>

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

Crashes

[Ken Rudolph]

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


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


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

Re: E MAIL CRASHES ON 2.48

[Frank-Rainer Grahl]

Source code is now fixed and we will upgrade the base to ESR 52.4 level. 
Building should continue soon.


I am not seeing the spinning wheel for long on a late 2012 mini mac with an 
imap account. Maybe its time to compact and/or rebuild the folders.


The Thunderbird devs fixed another bunch of annoyances in the shared code so 
hopefully any account problems will go away over time.


FRG


Gabriel wrote:

Frank-Rainer Grahl wrote on 25/09/17 18:58:
2.49.1 is currently being build but we ran into a problem with Lightning. 
The first candidate builds should work but Lightning 5.4 can not be 
installed If you do it is is broken. Fix is in the works but delays the 
version a bit unfortunately:


https://archive.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build1/mac/en-US/ 





Hi,

great :-) no more crashes when opening the Mail.

There are only 2 little annoying things:
1) When I open the Mail window for the first time, it takes a lot to ask for 
the accounts password (the spinning wheel stays for 30+ seconds);
2) sometimes it says I entered a wrong password (for all the acounts) while it 
didn't even contact the mail server.

But these are issues already present in SM since 2.40 as far as I can remember.

Anyway, SM 2.49.1 is working on El Capitan, thank you!


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

Re: E MAIL CRASHES ON 2.48

[Gabriel]

Frank-Rainer Grahl wrote on 25/09/17 18:58:
2.49.1 is currently being build but we ran into a problem with Lightning. The 
first candidate builds should work but Lightning 5.4 can not be installed If you 
do it is is broken. Fix is in the works but delays the version a bit unfortunately:


https://archive.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build1/mac/en-US/ 





Hi,

great :-) no more crashes when opening the Mail.

There are only 2 little annoying things:
1) When I open the Mail window for the first time, it takes a lot to ask for the 
accounts password (the spinning wheel stays for 30+ seconds);
2) sometimes it says I entered a wrong password (for all the acounts) while it 
didn't even contact the mail server.

But these are issues already present in SM since 2.40 as far as I can remember.

Anyway, SM 2.49.1 is working on El Capitan, thank you!

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

Re: E MAIL CRASHES ON 2.48

[Philipp van Hüllen]

Frank-Rainer Grahl wrote:
2.49.1 is currently being build but we ran into a problem with 
Lightning. The first candidate builds should work but Lightning 5.4 can 
not be installed If you do it is is broken. Fix is in the works but 
delays the version a bit unfortunately:


https://archive.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build1/mac/en-US/ 


Works for me. (Way better than 2.48; and I don't use Lightning.) :)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) 
Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1


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

Re: E MAIL CRASHES ON 2.48

[Frank-Rainer Grahl]

2.49.1 is currently being build but we ran into a problem with Lightning. The 
first candidate builds should work but Lightning 5.4 can not be installed If 
you do it is is broken. Fix is in the works but delays the version a bit 
unfortunately:


https://archive.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build1/mac/en-US/

The tinderbox builds use a slightly different source set but should work too 
and include Lightning:


https://archive.mozilla.org/pub/seamonkey/tinderbox-builds/comm-esr-macosx64/1506101503/

If you try one please backup your profile. The OSX startup and mail crashes 
should be fixed in both.


FRG

Gabriel wrote:

Frank-Rainer Grahl wrote on 03/08/17 08:04:

It is probably bug 1286613:

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

Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not sure 
if we

can backport all the parts to 2.48 and do a 2.48.1

I tested 2.48 including mail in 10.12.6 and it worked for me so not everyone
seems to be affected. If you are still on 10.11.x or lower you should be 
good too.



Hello,

I waited until today to try the 2.48 for Mac, but I confirm it crashes as soon 
as you open the Mail window.


In the "known issues" page 
(https://www.seamonkey-project.org/releases/seamonkey2.48/#new) it's written 
this happens with macOS 10.12 but I'm using El Capitan (OS X 10.11.6) and it 
crashes.

I had to reinstall SM 2.46

Eg:
https://crash-stats.mozilla.com/report/index/456c0c04-feb1-4ffb-8998-99e8b0170925



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

Re: E MAIL CRASHES ON 2.48

[Gabriel]

Frank-Rainer Grahl wrote on 03/08/17 08:04:

It is probably bug 1286613:

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

Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not sure if we
can backport all the parts to 2.48 and do a 2.48.1

I tested 2.48 including mail in 10.12.6 and it worked for me so not everyone
seems to be affected. If you are still on 10.11.x or lower you should be good 
too.



Hello,

I waited until today to try the 2.48 for Mac, but I confirm it crashes as soon 
as you open the Mail window.


In the "known issues" page 
(https://www.seamonkey-project.org/releases/seamonkey2.48/#new) it's written 
this happens with macOS 10.12 but I'm using El Capitan (OS X 10.11.6) and it 
crashes.

I had to reinstall SM 2.46

Eg:
https://crash-stats.mozilla.com/report/index/456c0c04-feb1-4ffb-8998-99e8b0170925


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

Re: E MAIL CRASHES ON 2.48

[Frank-Rainer Grahl]

> I jumped on the ESR as soon as Adrian published it.
> The source code is ready, it just needs to be compiled.

Nope. Just found out the OS X bug wasn't fixed for 52. TB took it into a 
branch. We need to do the same or maybe use the branch from the next TB which 
should be due soon.


There were some real problems in early 2.49 builds. The last ones got just 
fixed last week. Browsing was usually fine but mail had it share of them. Look 
at reports for early TB 52 versions. A lot of unhappy campers out there. Most 
were caused by changes in mozilla code which tightened security or just 
changed something... Thankfully the TB devs fixed the nasty ones so that we 
can profit from their work.


FRG

Mason83 wrote:

On 04/08/2017 14:34, WaltS48 wrote:

On 8/4/17 3:06 AM, Mason83 wrote:

On 04/08/2017 04:12, Edmund Wong wrote:

Frank-Rainer Grahl wrote:

It is probably bug 1286613:

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

Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not
sure if we can backport all the parts to 2.48 and do a 2.48.1


It is worth doing that if it fixes problems.


Isn't it far simpler to push a 2.49.1 release?


How long did you have to wait for 2.48?


I jumped on the ESR as soon as Adrian published it.
The source code is ready, it just needs to be compiled.

I don't understand the difference between Adrian's builds
and official builds...

Regards.


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

Re: E MAIL CRASHES ON 2.48

[Mason83]

On 04/08/2017 14:34, WaltS48 wrote:
> On 8/4/17 3:06 AM, Mason83 wrote:
>> On 04/08/2017 04:12, Edmund Wong wrote:
>>> Frank-Rainer Grahl wrote:
 It is probably bug 1286613:

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

 Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not
 sure if we can backport all the parts to 2.48 and do a 2.48.1
>>>
>>> It is worth doing that if it fixes problems.
>>
>> Isn't it far simpler to push a 2.49.1 release?
> 
> How long did you have to wait for 2.48?

I jumped on the ESR as soon as Adrian published it.
The source code is ready, it just needs to be compiled.

I don't understand the difference between Adrian's builds
and official builds...

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

Re: E MAIL CRASHES ON 2.48

[WaltS48]

On 8/4/17 3:06 AM, Mason83 wrote:

On 04/08/2017 04:12, Edmund Wong wrote:

Frank-Rainer Grahl wrote:

It is probably bug 1286613:

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

Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not
sure if we can backport all the parts to 2.48 and do a 2.48.1


It is worth doing that if it fixes problems.


Isn't it far simpler to push a 2.49.1 release?

Regards.



How long did you have to wait for 2.48?

Probably not far simpler.

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

Re: E MAIL CRASHES ON 2.48

[Mason83]

On 04/08/2017 04:12, Edmund Wong wrote:
> Frank-Rainer Grahl wrote:
>> It is probably bug 1286613:
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=1286613
>>
>> Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not
>> sure if we can backport all the parts to 2.48 and do a 2.48.1
> 
> It is worth doing that if it fixes problems.

Isn't it far simpler to push a 2.49.1 release?

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

Re: E MAIL CRASHES ON 2.48

[Edmund Wong]

Frank-Rainer Grahl wrote:
> It is probably bug 1286613:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1286613
> 
> Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not
> sure if we can backport all the parts to 2.48 and do a 2.48.1

It is worth doing that if it fixes problems.

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

Re: E MAIL CRASHES ON 2.48

[WaltS48]

On 8/3/17 1:56 PM, wwel...@gmail.com wrote:

On Thursday, August 3, 2017 at 3:47:35 AM UTC-4, null wrote:

wwel...@gmail.com wrote:

On Wednesday, August 2, 2017 at 3:42:27 PM UTC-4, wwe...@gmail.com wrote:

I have a Mac and just downloaded SM 2.48. The problem is that when I attempt to 
open an e mail the whole program crashed!

What can I do to fix this?  Thanks.

Now for unknown reason (after I tried to restart SM) it doesn't even open!!

I'm back to where every time I try to open SM it doesn't open but crashes 
immediately!

What is going on here??

Surely the thing to do at this point is to see what happens if you
simply re-install 2.48? Have you done that? There could be a glitch on
your HD affecting a key file or files.


Thanks but I don't even want to attempt it and go through what I went though 
yesterday! It's working fine so that's all I care right now. What does 2.48 do 
that 2.46 doesn't?



Security. My number one priority regarding all software.

SeaMonkey 2.48 uses the same backend as Firefox and contains the listed Firefox 51.0.3 security fixes". 


That includes the four critical security vulnerabilities fixed in 
Firefox 51 and the one fixed in 51.0.3, among others that aren't listed 
as critical.


<https://www.mozilla.org/en-US/security/advisories/mfsa2017-01/>

<https://www.mozilla.org/en-US/security/advisories/mfsa2017-04/>

See the Release Notes for other changes.

<https://www.seamonkey-project.org/releases/seamonkey2.48/>

--
Go Bucs!
Coexist <https://www.coexist.org/>
National Popular Vote <http://www.nationalpopularvote.com/>
Ubuntu 16.04 LTS - Unity Desktop
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: E MAIL CRASHES ON 2.48

[wwelvis]

On Thursday, August 3, 2017 at 3:47:35 AM UTC-4, null wrote:
> wwel...@gmail.com wrote:
> > On Wednesday, August 2, 2017 at 3:42:27 PM UTC-4, wwe...@gmail.com wrote:
> >> I have a Mac and just downloaded SM 2.48. The problem is that when I 
> >> attempt to open an e mail the whole program crashed!
> >>
> >> What can I do to fix this?  Thanks.
> > Now for unknown reason (after I tried to restart SM) it doesn't even open!!
> >
> > I'm back to where every time I try to open SM it doesn't open but crashes 
> > immediately!
> >
> > What is going on here??
> Surely the thing to do at this point is to see what happens if you 
> simply re-install 2.48? Have you done that? There could be a glitch on 
> your HD affecting a key file or files.

Thanks but I don't even want to attempt it and go through what I went though 
yesterday! It's working fine so that's all I care right now. What does 2.48 do 
that 2.46 doesn't?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: E MAIL CRASHES ON 2.48

[null]

wwel...@gmail.com wrote:

On Wednesday, August 2, 2017 at 3:42:27 PM UTC-4, wwe...@gmail.com wrote:

I have a Mac and just downloaded SM 2.48. The problem is that when I attempt to 
open an e mail the whole program crashed!

What can I do to fix this?  Thanks.

Now for unknown reason (after I tried to restart SM) it doesn't even open!!

I'm back to where every time I try to open SM it doesn't open but crashes 
immediately!

What is going on here??
Surely the thing to do at this point is to see what happens if you 
simply re-install 2.48? Have you done that? There could be a glitch on 
your HD affecting a key file or files.

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

Re: E MAIL CRASHES ON 2.48

[Frank-Rainer Grahl]

It is probably bug 1286613:

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

Solution is unfortunately to go back to 2.46 and wait for 2.49.1. Not 
sure if we can backport all the parts to 2.48 and do a 2.48.1


I tested 2.48 including mail in 10.12.6 and it worked for me so not 
everyone seems to be affected. If you are still on 10.11.x or lower you 
should be good too.


FRG


wwel...@gmail.com wrote:

On Wednesday, August 2, 2017 at 4:00:29 PM UTC-4, Adrian Kalla wrote:

02.08.2017 21:59, Adrian Kalla:

  02.08.2017 21:42, wwel...@gmail.com:

I have a Mac and just downloaded SM 2.48. The problem is that when I attempt to 
open an e mail the whole program crashed!


or... did you mean opening an existing email or creating a new one?


I mean opening either an old one or one that is new!!



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

Re: E MAIL CRASHES ON 2.48

[wwelvis]

On Wednesday, August 2, 2017 at 3:42:27 PM UTC-4, wwe...@gmail.com wrote:
> I have a Mac and just downloaded SM 2.48. The problem is that when I attempt 
> to open an e mail the whole program crashed!
> 
> What can I do to fix this?  Thanks.

Now for unknown reason (after I tried to restart SM) it doesn't even open!!

I'm back to where every time I try to open SM it doesn't open but crashes 
immediately!

What is going on here??
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: E MAIL CRASHES ON 2.48

[wwelvis]

On Wednesday, August 2, 2017 at 4:00:29 PM UTC-4, Adrian Kalla wrote:
> 02.08.2017 21:59, Adrian Kalla:
> >  02.08.2017 21:42, wwel...@gmail.com:
> >> I have a Mac and just downloaded SM 2.48. The problem is that when I 
> >> attempt to open an e mail the whole program crashed!
> 
> or... did you mean opening an existing email or creating a new one?

I mean opening either an old one or one that is new!!
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: E MAIL CRASHES ON 2.48

[Adrian Kalla]

02.08.2017 21:59, Adrian Kalla:
>  02.08.2017 21:42, wwel...@gmail.com:
>> I have a Mac and just downloaded SM 2.48. The problem is that when I attempt 
>> to open an e mail the whole program crashed!

or... did you mean opening an existing email or creating a new one?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: E MAIL CRASHES ON 2.48

[Adrian Kalla]

 02.08.2017 21:42, wwel...@gmail.com:
> I have a Mac and just downloaded SM 2.48. The problem is that when I attempt 
> to open an e mail the whole program crashed!

This was supposed to be fixed in 2.48...:
https://bugzilla.mozilla.org/show_bug.cgi?id=1364977

Core bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=1308923
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

E MAIL CRASHES ON 2.48

[wwelvis]

I have a Mac and just downloaded SM 2.48. The problem is that when I attempt to 
open an e mail the whole program crashed!

What can I do to fix this?  Thanks.
___
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 <https://www.coexist.org/>
National Popular Vote <http://www.nationalpopularvote.com/>
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

Crashes

[Ken Rudolph]

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.

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

Re: Password manager crashes SeaMonkey

[Frank-Rainer Grahl]

> Something has been changed .

Access to storage was broken in previous versions so naturally its 
slower now because it actually accesses it again.


Doesn't help that every time Data Manager is opened the complete list is 
refreshed 2 times. I looked at it briefly but I think it needs a rewrite 
and switch to asynchronous processing. If SeaMonkey weathers the XUL 
removal storm I will look into it. Not worth it now.


FRG

Ray_Net wrote:

Bob Minchin wrote on 06-02-17 22:29:

As per subject.



I don't have a crash BUT:

When I was in SM 2.40 "data manager" access was in les than a second.
Now with SM 2.46 "data manager" is usuable only after 7 seconds.

Something has been changed .


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

Re: Password manager crashes SeaMonkey

[Ray_Net]

Bob Minchin wrote on 06-02-17 22:29:

As per subject.

Seamonkey 2.46
Win XP SP3

As soon as I open up password manager, the application locks up and I 
have to kill it using Cntl Alt Del


Any clues please?

Tia
Bob


I don't have a crash BUT:

When I was in SM 2.40 "data manager" access was in les than a second.
Now with SM 2.46 "data manager" is usuable only after 7 seconds.

Something has been changed .
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Re: [webappsstore.sqlite files ] Re: Password manager crashes SeaMonkey

[Frank-Rainer Grahl]

Usually this is used by websites to store offsite data. Sometimes also 
something called supercookies just used to track you.


Under preferences-> Advanced->Offline Web Application you should see if 
something is stored. That can undermine you privacy pretty fast so I 
usually have it disabled. You usually can delete the file. Any needed 
data will be stored again. If unsure move it out of the profile and only 
restore it if you experience problems.


FRG


Ray_Net wrote:
I don't have this problem ...however I see in the profile directory 
those files:

webappsstore.sqlite   43 MB dated 07-02-17 18:33
webappsstore.sqlite-shm 32KB dated 07-02-17 21:59
webappsstore.sqlite-wl 3KB dated 07-02-17 23:35

It looks that those files are used, BUT I never use SM offline.

So what ? Is it a good idea, when SM is not running to delete those 3 
files to gain 43MB ?  I dont know what's inside those files ... So 
better avoid the deletion ?


Frank-Rainer Grahl wrote on 06-02-17 22:55:
So far most problems with a hung data manager (which password manager 
is a part of) seem to point to an obsolete and bloated 
webappsstore.sqlite in your profile. Please close SeaMonkey and rename 
(or delet if you are sure you don't need the data in it) this file. It 
contains offline website storage. Then check again.


FRG


Bob Minchin wrote:

As per subject.

Seamonkey 2.46
Win XP SP3

As soon as I open up password manager, the application locks up and I 
have to kill it using Cntl Alt Del


Any clues please?

Tia
Bob






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

Re: [webappsstore.sqlite files ] Re: Password manager crashes SeaMonkey

[Verwayne Greenhoe]

I was having this issue with the SM 2.48 version. If I went to check on a
password, it would lock the browser up tight for several minutes. After
reading about the issue with the 'webappsstore.sqlite' issue, I went into
my profile, opened it, closed down SM, and then changed the name to
webappsstorea.sqlite and the issue went away. If I should ever need it,
it's still there. Other than that, I've little other problems.

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

[webappsstore.sqlite files ] Re: Password manager crashes SeaMonkey

[Ray_Net]

I don't have this problem ...however I see in the profile directory 
those files:

webappsstore.sqlite   43 MB dated 07-02-17 18:33
webappsstore.sqlite-shm 32KB dated 07-02-17 21:59
webappsstore.sqlite-wl 3KB dated 07-02-17 23:35

It looks that those files are used, BUT I never use SM offline.

So what ? Is it a good idea, when SM is not running to delete those 3 
files to gain 43MB ?  I dont know what's inside those files ... So 
better avoid the deletion ?


Frank-Rainer Grahl wrote on 06-02-17 22:55:
So far most problems with a hung data manager (which password manager 
is a part of) seem to point to an obsolete and bloated 
webappsstore.sqlite in your profile. Please close SeaMonkey and rename 
(or delet if you are sure you don't need the data in it) this file. It 
contains offline website storage. Then check again.


FRG


Bob Minchin wrote:

As per subject.

Seamonkey 2.46
Win XP SP3

As soon as I open up password manager, the application locks up and I 
have to kill it using Cntl Alt Del


Any clues please?

Tia
Bob




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

Re: Password manager crashes SeaMonkey

[Frank-Rainer Grahl]

So far most problems with a hung data manager (which password manager is a 
part of) seem to point to an obsolete and bloated webappsstore.sqlite in your 
profile. Please close SeaMonkey and rename (or delet if you are sure you don't 
need the data in it) this file. It contains offline website storage. Then 
check again.


FRG


Bob Minchin wrote:

As per subject.

Seamonkey 2.46
Win XP SP3

As soon as I open up password manager, the application locks up and I have to 
kill it using Cntl Alt Del


Any clues please?

Tia
Bob


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

Password manager crashes SeaMonkey

[Bob Minchin]

As per subject.

Seamonkey 2.46
Win XP SP3

As soon as I open up password manager, the application locks up and I 
have to kill it using Cntl Alt Del


Any clues please?

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

Password manager Crashes SeaMonkey

[Bob Minchin]

As per subject.

Seamonkey 2.46
Win XP SP3

As soon as I open up password manager, the application locks up and I 
have to kill it using Cntl Alt Del


Any clues please?

Tia
Bob
___
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