Re: Crashes

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

Re: Crashes

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

Re: Crashes

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.

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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.

Re: Crashes

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.

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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:

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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,

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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. 

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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:

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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.

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

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

Re: Crashes

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.

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

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

Re: Crashes

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

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

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.

Re: Crashes

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

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

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

Re: Crashes

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.

Re: Crashes

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.

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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.

Re: Crashes

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

Re: Crashes

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

Re: Crashes

TCW wrote: On 1/17/2017 8:40 PM, JAS wrote: TCW wrote: On 1/16/2017 11:08 AM, JAS wrote: I have had several crashes lately and wonder if someone can decipher the crash reports? Using SM 2.48 on Win 7 Pro Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 -

Re: Crashes

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

Re: Crashes

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

Re: Crashes

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

Re: Crashes

On 17/01/2017 19:46, TCW wrote: > From your crash report: Available Physical Memory: 5,169,344,512 bytes > (4.81 GB)huh? How is this even possible? Available physical memory > is at 4.81GB on x86? Do you have 8GB installed on an x86 machine? PAE > running? I see you page file is at 12GB

Re: Crashes

On 1/17/2017 8:40 PM, JAS wrote: TCW wrote: On 1/16/2017 11:08 AM, JAS wrote: I have had several crashes lately and wonder if someone can decipher the crash reports? Using SM 2.48 on Win 7 Pro Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 - Build ID:

Re: Crashes

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

Re: Crashes

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

Re: Crashes

> I know, and they don't even have a Beta build yet. Wonder what the reason for > that is, or did I just miss it at: Beta progress is tracked in Bug 1328886: https://bugzilla.mozilla.org/show_bug.cgi?id=1328886 As usual build config changes and the odd bug or two. Nothing serious so far. It

Re: Crashes

On 01/16/2017 05:36 PM, David E. Ross wrote: On 1/16/2017 1:40 PM, WaltS48 wrote: On 01/16/2017 02:56 PM, David E. Ross wrote: On 1/16/2017 9:08 AM, JAS wrote: I have had several crashes lately and wonder if someone can decipher the crash reports? Using SM 2.48 on Win 7 Pro Mozilla/5.0

Re: Crashes

On 1/16/2017 1:40 PM, WaltS48 wrote: > On 01/16/2017 02:56 PM, David E. Ross wrote: >> On 1/16/2017 9:08 AM, JAS wrote: >>> I have had several crashes lately and wonder if someone can decipher the >>> crash reports? Using SM 2.48 on Win 7 Pro >>> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0)

Re: Crashes

On 01/16/2017 02:56 PM, David E. Ross wrote: On 1/16/2017 9:08 AM, JAS wrote: I have had several crashes lately and wonder if someone can decipher the crash reports? Using SM 2.48 on Win 7 Pro Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 - Build ID:

Re: Crashes

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

Re: Crashes

Frank-Rainer Grahl wrote: Looks like these come from Adrians or local builds. Unfortunately they do not have symbols so the crash reports are almost useless. Do you know what you did when SeaMonkey crashed? It sounds like the same problem mason385 reported. There are a few bug reports against

Re: Crashes

Looks like these come from Adrians or local builds. Unfortunately they do not have symbols so the crash reports are almost useless. Do you know what you did when SeaMonkey crashed? It sounds like the same problem mason385 reported. There are a few bug reports against the mailnews component

Re: Crashes

On 12-06-01 10:10 PM, Alex wrote: On 6/1/2012 7:47 PM, Chris Ilias wrote: On 12-06-01 6:06 PM, Alex wrote: In the last several months since upgrading to new version my SM has been randomly crashing. I tried to run it in safe mode but problem persisted. I was hoping that with new upgrade it's

Re: Crashes

On 6/2/2012 3:49 PM, Chris Ilias wrote: On 12-06-01 10:10 PM, Alex wrote: On 6/1/2012 7:47 PM, Chris Ilias wrote: On 12-06-01 6:06 PM, Alex wrote: In the last several months since upgrading to new version my SM has been randomly crashing. I tried to run it in safe mode but problem persisted.

Re: Crashes

Alex wrote: On 6/2/2012 3:49 PM, Chris Ilias wrote: On 12-06-01 10:10 PM, Alex wrote: On 6/1/2012 7:47 PM, Chris Ilias wrote: On 12-06-01 6:06 PM, Alex wrote: In the last several months since upgrading to new version my SM has been randomly crashing. I tried to run it in safe mode but

Re: Crashes

On 12-06-01 6:06 PM, Alex wrote: In the last several months since upgrading to new version my SM has been randomly crashing. I tried to run it in safe mode but problem persisted. I was hoping that with new upgrade it's be resolved but nothing changed. The crashes happening on my laptop, notebook

Re: Crashes

On 6/1/2012 7:47 PM, Chris Ilias wrote: On 12-06-01 6:06 PM, Alex wrote: In the last several months since upgrading to new version my SM has been randomly crashing. I tried to run it in safe mode but problem persisted. I was hoping that with new upgrade it's be resolved but nothing changed. The

Re: Crashes When Printing

Chris Ilias a écrit : On 11-11-02 12:01 AM, Sandy Pamin wrote: ID: d07f1d26-9787-4ff2-9637-a2d9f201 Signature: F_1359172165 That crash is caused by the Flash plugin. I don't remember if the plugin crash protection feature was implemented before or after SM

Re: Crashes When Printing

On 11-11-02 12:01 AM, Sandy Pamin wrote: ID: d07f1d26-9787-4ff2-9637-a2d9f201 Signature: F_1359172165 That crash is caused by the Flash plugin. I don't remember if the plugin crash protection feature was implemented before or after SM 2.0.14; but you should

Re: Crashes When Printing

Chris Ilias schrieb: I don't remember if the plugin crash protection feature was implemented before or after SM 2.0.14 After. You need 2.1 or higher to have plugin crash protection. And we have been fixing a lot of crashes in recent times, so anyone seeing crashes should get to at least the

Re: Crashes When Printing

Sandy Pamin schrieb: Seamonkey 2.0.14 has been crashing a lot lately when trying to print. Please try 2.4.1, it's easily possible that this has been fixed there. We are steadily working on fixing crashes in all Mozilla products. Robert Kaiser -- Note that any statements of mine - no

Re: Crashes When Printing

Sandy Pamin wrote: JD wrote: Sandy Pamin wrote: Seamonkey 2.0.14 has been crashing a lot lately when trying to print. I get the Mozilla Crash Reporter. I happens with all 4 of my PC's, both Win XP and Win 7. Pages print fine with IE. Any ideas? about:crashes Copy and paste one report in

Re: Crashes When Printing

Sandy Pamin wrote: Seamonkey 2.0.14 has been crashing a lot lately when trying to print. I get the Mozilla Crash Reporter. I happens with all 4 of my PC's, both Win XP and Win 7. Pages print fine with IE. Any ideas? about:crashes Copy and paste one report in your reply so somebody can take a

Re: Crashes When Printing

JD wrote: Sandy Pamin wrote: Seamonkey 2.0.14 has been crashing a lot lately when trying to print. I get the Mozilla Crash Reporter. I happens with all 4 of my PC's, both Win XP and Win 7. Pages print fine with IE. Any ideas? about:crashes Copy and paste one report in your reply so somebody

Re: crashes in flash

cyberzen a écrit : cyberzen a écrit : ID: 6a55d3c8-0813-44b2-a12a-331d52110323 Signature: F1292875159_ with flashblock on I have one per day approx SM 2.0.13 will not solve this I suppose.. that did not.. but.. as I found a site

Re: crashes in flash

On 3/25/11 1:15 AM, cyberzen wrote: cyberzen a écrit : cyberzen a écrit : ID: 6a55d3c8-0813-44b2-a12a-331d52110323 Signature: F1292875159_ with flashblock on I have one per day approx SM 2.0.13 will not solve this I suppose.. that did not.. but..

Re: crashes in flash

David E. Ross a écrit : On 3/25/11 1:15 AM, cyberzen wrote: cyberzen a écrit : cyberzen a écrit : ID: 6a55d3c8-0813-44b2-a12a-331d52110323 Signature: F1292875159_ with flashblock on I have one per day approx SM 2.0.13 will not solve this I suppose..

Re: crashes in flash

cyberzen a écrit : ID: 6a55d3c8-0813-44b2-a12a-331d52110323 Signature: F1292875159_ with flashblock on I have one per day approx SM 2.0.13 will not solve this I suppose.. -- cyberzen ___ support-seamonkey

Re: crashes in flash

On 3/23/11 1:44 AM, cyberzen wrote: ID: 6a55d3c8-0813-44b2-a12a-331d52110323 Signature: F1292875159_ with flashblock on I have one per day approx I have not seen this problem. Is it possible you have a bad installation of Flash? The NPSWF32.dll

Re: crashes in flash

David E. Ross a écrit : On 3/23/11 1:44 AM, cyberzen wrote: ID: 6a55d3c8-0813-44b2-a12a-331d52110323 Signature: F1292875159_ with flashblock on I have one per day approx I have not seen this problem. Is it possible you have a bad installation of

Re: Crashes after 2.0.7 update - possible fix

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

Re: Crashes after 2.0.7 update - possible fix

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

Re: Crashes after 2.0.7 update - possible fix

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

Re: Crashes after 2.0.7 update - possible fix

JOLAN1 schrieb: On Sep 8, 6:16 pm, Robert Kaiserka...@kairo.at wrote: Hi, If you are seeing a crash (probably when profile manager should come up) after getting an update to 2.0.7, please try to go into the SeaMonkey application/install folder, find a subfolder named components and remove the

Re: Crashes after 2.0.7 update - possible fix

Robert Kaiser wrote: JOLAN1 schrieb: On Sep 8, 6:16 pm, Robert Kaiserka...@kairo.at wrote: Hi, If you are seeing a crash (probably when profile manager should come up) after getting an update to 2.0.7, please try to go into the SeaMonkey application/install folder, find a subfolder named

Re: Crashes after 2.0.7 update - possible fix

David Wilkinson schrieb: Robert Kaiser wrote: JOLAN1 schrieb: On Sep 8, 6:16 pm, Robert Kaiserka...@kairo.at wrote: Hi, If you are seeing a crash (probably when profile manager should come up) after getting an update to 2.0.7, please try to go into the SeaMonkey application/install folder,