Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-03-04 Thread Pat Welch

JAS wrote:

Pat Welch wrote:

MintyJewel wrote:

On Feb 5, 5:34 pm, Pat Welchpat...@inreach.com   wrote:

Hi.

This has gotten to the point I'm going to have to abandon SM 2.x
soon. I
never saw this in any 1.x version.

I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
Turion dual-core chip, 3 MB RAM.

After about 8 hours of use, suddenly the browser stops working in a
curious way - clicking on a bookmark or an embedded URL silently
presents a blank page, no complaints, just no pages will display.

Email continues to work, until I close all Seamonkey instances while
trying to fix the problem.

What happens then is Seamonkey pops up a box that complains it is
already running, and to close that Seamonkey before trying to run.

But there are no visible instances of Seamonkey running.

Going to the Task Manager, I see an instance of Seamonkey IS
running. So
I kill it in Task Manager.
Then I kill it again.
Then I kill it again ... etc. etc.

The Seamonkey process is unkillable.

I have to at this point re-boot before the browser starts working
again.

What can I do to help get this fixed? There is no crash report because
Seamonkey is unaware it's munged and unreachable.

Help!

--

Pat Welch, UBB Computer Services, a WCS Affiliate
  SCO Authorized Partner
  Microlite BackupEdge Certified Reseller
  Unix/Linux/Windows/Hardware Sales/Support
  (209) 745-1401 Cell: (209) 251-9120
  E-mail: pat...@inreach.com



Pat,

Download System Exployer:
http://technet.microsoft.com/en-us/sysinternals/default.aspx

You CAN kill the unkillable. You may also verify files, track their
paths, and
also it's used for stacking logs and debugging.

It's a wonderful little program I've used for a few years now.

oh and there's no cost.


Umm, no joy.

Unkillable Seamonkey is still unkillable.

The sysinternals are just for the most part front-ends to primitives -
and the kill functions call the same kill function that the Task
Manager does.

So the only way to get back the browser is to re-boot. How very 1995
of the developers.

BTW, I'm on 2.0.3 - same problem, the browser dies silently, and if
you end out of all the instances of Seamonkey you are left with an
absolutely un-killable version of Seamonkey still in the process list.



I also am running SM 2.0.3 and have no problem going into the task
manager an killing Seamonkey if I desire, but I have ended out of all
the instances of Seamonkey and it is GONE. I have very few problems with
SM 2.0.3 and like it very much. Perhaps an extension?



I'm on Vista, and I think you are running XP from your header. Different 
ballpark as it were.


I think I'll give the latest Opera a look, I'm tired of re-booting.

--

Pat Welch, UBB Computer Services, a WCS Affiliate
   SCO Authorized Partner
   Microlite BackupEdge Certified Reseller
   Unix/Linux/Windows/Hardware Sales/Support
   (209) 745-1401 Cell: (209) 251-9120
   E-mail: pat...@inreach.com

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


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-03-03 Thread Pat Welch

MintyJewel wrote:

On Feb 5, 5:34 pm, Pat Welchpat...@inreach.com  wrote:

Hi.

This has gotten to the point I'm going to have to abandon SM 2.x soon. I
never saw this in any 1.x version.

I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
Turion dual-core chip, 3 MB RAM.

After about 8 hours of use, suddenly the browser stops working in a
curious way - clicking on a bookmark or an embedded URL silently
presents a blank page, no complaints, just no pages will display.

Email continues to work, until I close all Seamonkey instances while
trying to fix the problem.

What happens then is Seamonkey pops up a box that complains it is
already running, and to close that Seamonkey before trying to run.

But there are no visible instances of Seamonkey running.

Going to the Task Manager, I see an instance of Seamonkey IS running. So
I kill it in Task Manager.
Then I kill it again.
Then I kill it again ... etc. etc.

The Seamonkey process is unkillable.

I have to at this point re-boot before the browser starts working again.

What can I do to help get this fixed? There is no crash report because
Seamonkey is unaware it's munged and unreachable.

Help!

--

Pat Welch, UBB Computer Services, a WCS Affiliate
 SCO Authorized Partner
 Microlite BackupEdge Certified Reseller
 Unix/Linux/Windows/Hardware Sales/Support
 (209) 745-1401 Cell: (209) 251-9120
 E-mail: pat...@inreach.com



Pat,

Download System Exployer:
http://technet.microsoft.com/en-us/sysinternals/default.aspx

You CAN kill the unkillable. You may also verify files, track their
paths, and
also it's used for stacking logs and debugging.

It's a wonderful little program I've used for a few years now.

oh and there's no cost.


Umm, no joy.

Unkillable Seamonkey is still unkillable.

The sysinternals are just for the most part front-ends to primitives - 
and the kill functions call the same kill function that the Task Manager 
does.


So the only way to get back the browser is to re-boot. How very 1995 of 
the developers.


BTW, I'm on 2.0.3 - same problem, the browser dies silently, and if you 
end out of all the instances of Seamonkey you are left with an 
absolutely un-killable version of Seamonkey still in the process list.



--

Pat Welch, UBB Computer Services, a WCS Affiliate
   SCO Authorized Partner
   Microlite BackupEdge Certified Reseller
   Unix/Linux/Windows/Hardware Sales/Support
   (209) 745-1401 Cell: (209) 251-9120
   E-mail: pat...@inreach.com

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


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-03-03 Thread JAS
Pat Welch wrote:
 MintyJewel wrote:
 On Feb 5, 5:34 pm, Pat Welchpat...@inreach.com  wrote:
 Hi.

 This has gotten to the point I'm going to have to abandon SM 2.x
 soon. I
 never saw this in any 1.x version.

 I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
 Turion dual-core chip, 3 MB RAM.

 After about 8 hours of use, suddenly the browser stops working in a
 curious way - clicking on a bookmark or an embedded URL silently
 presents a blank page, no complaints, just no pages will display.

 Email continues to work, until I close all Seamonkey instances while
 trying to fix the problem.

 What happens then is Seamonkey pops up a box that complains it is
 already running, and to close that Seamonkey before trying to run.

 But there are no visible instances of Seamonkey running.

 Going to the Task Manager, I see an instance of Seamonkey IS
 running. So
 I kill it in Task Manager.
 Then I kill it again.
 Then I kill it again ... etc. etc.

 The Seamonkey process is unkillable.

 I have to at this point re-boot before the browser starts working
 again.

 What can I do to help get this fixed? There is no crash report because
 Seamonkey is unaware it's munged and unreachable.

 Help!

 -- 
 
 Pat Welch, UBB Computer Services, a WCS Affiliate
  SCO Authorized Partner
  Microlite BackupEdge Certified Reseller
  Unix/Linux/Windows/Hardware Sales/Support
  (209) 745-1401 Cell: (209) 251-9120
  E-mail: pat...@inreach.com
 

 Pat,

 Download System Exployer:
 http://technet.microsoft.com/en-us/sysinternals/default.aspx

 You CAN kill the unkillable. You may also verify files, track their
 paths, and
 also it's used for stacking logs and debugging.

 It's a wonderful little program I've used for a few years now.

 oh and there's no cost.

 Umm, no joy.

 Unkillable Seamonkey is still unkillable.

 The sysinternals are just for the most part front-ends to primitives -
 and the kill functions call the same kill function that the Task
 Manager does.

 So the only way to get back the browser is to re-boot. How very 1995
 of the developers.

 BTW, I'm on 2.0.3 - same problem, the browser dies silently, and if
 you end out of all the instances of Seamonkey you are left with an
 absolutely un-killable version of Seamonkey still in the process list.


I also am running SM 2.0.3 and have no problem going into the task
manager an killing Seamonkey if I desire, but I have ended out of all
the instances of Seamonkey and it is GONE. I have very few problems with
SM 2.0.3 and like it very much. Perhaps an extension?

-- 
   You either teach people to treat you with dignity and respect, or you don't. 
This means you are partly responsible for the mistreatment that you get at the 
hands of someone else. 

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


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-02-28 Thread MintyJewel
On Feb 5, 5:34 pm, Pat Welch pat...@inreach.com wrote:
 Hi.

 This has gotten to the point I'm going to have to abandon SM 2.x soon. I
 never saw this in any 1.x version.

 I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
 Turion dual-core chip, 3 MB RAM.

 After about 8 hours of use, suddenly the browser stops working in a
 curious way - clicking on a bookmark or an embedded URL silently
 presents a blank page, no complaints, just no pages will display.

 Email continues to work, until I close all Seamonkey instances while
 trying to fix the problem.

 What happens then is Seamonkey pops up a box that complains it is
 already running, and to close that Seamonkey before trying to run.

 But there are no visible instances of Seamonkey running.

 Going to the Task Manager, I see an instance of Seamonkey IS running. So
 I kill it in Task Manager.
 Then I kill it again.
 Then I kill it again ... etc. etc.

 The Seamonkey process is unkillable.

 I have to at this point re-boot before the browser starts working again.

 What can I do to help get this fixed? There is no crash report because
 Seamonkey is unaware it's munged and unreachable.

 Help!

 --
 
 Pat Welch, UBB Computer Services, a WCS Affiliate
             SCO Authorized Partner
             Microlite BackupEdge Certified Reseller
             Unix/Linux/Windows/Hardware Sales/Support
             (209) 745-1401 Cell: (209) 251-9120
             E-mail: pat...@inreach.com
 

Pat,

Download System Exployer:
http://technet.microsoft.com/en-us/sysinternals/default.aspx

You CAN kill the unkillable. You may also verify files, track their
paths, and
also it's used for stacking logs and debugging.

It's a wonderful little program I've used for a few years now.

oh and there's no cost.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-02-09 Thread P.N.

Hello Pat,

I've got some problems with different software on Vista (not with SM, 
though), and cannot see complaints from other Vista users. So I guess, 
Your problems will more likely have sth. to do with Your Vista config 
than with SeaMonkey. But You'll have to give more information about Your 
problems, so somebody might be able to help You :-(


Kind regards

P.



Pat Welch wrote:

[snip]

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


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-02-09 Thread Pat Welch

P.N. wrote:

Hello Pat,

I've got some problems with different software on Vista (not with SM,
though), and cannot see complaints from other Vista users. So I guess,
Your problems will more likely have sth. to do with Your Vista config
than with SeaMonkey. But You'll have to give more information about Your
problems, so somebody might be able to help You :-(

Kind regards

P.



Pat Welch wrote:

[snip]


Well, P., to summarize the problem:

1) The Seamonkey browser stops working after running around 8 hours
2) It stops on random sites, including sites that I visit all the time
3) It does not stop at the same site(s)
4) Closing all visible Seamonkey Windows results in a *completely* 
unkillable hidden Seamonkey process that prevents re-launching SeaMonkey 
(Complaining Seamonkey is already running)
5) Seamonkey apparently thinks it has NOT crashed and therefore can NOT 
generate a crash report ...
6) New info - I can run the IE 8 browser with no problems while 
Seamonkey has it's head buried in the sand, suggesting nothing is wrong 
with my ISP (Comcast) or my internal network or my firewall/router or my 
AV (Grisoft).


All facts I brought out in my 1st Email and repeated in the 2nd Email - 
perhaps someone with a better knowledge of the Vista Seamonkey internals 
can suggest how to force an error report or some other action I can take 
to obtain the magical more information you seek.


--

Pat Welch, UBB Computer Services, a WCS Affiliate
   SCO Authorized Partner
   Microlite BackupEdge Certified Reseller
   Unix/Linux/Windows/Hardware Sales/Support
   (209) 745-1401 Cell: (209) 251-9120
   E-mail: pat...@inreach.com

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


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-02-09 Thread Ray_Net

Rick Merrill wrote:

Pat Welch wrote:

Hi.

This has gotten to the point I'm going to have to abandon SM 2.x soon. I
never saw this in any 1.x version.

I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
Turion dual-core chip, 3 MB RAM.

After about 8 hours of use, suddenly the browser stops working in a
curious way - clicking on a bookmark or an embedded URL silently
presents a blank page, no complaints, just no pages will display.

Email continues to work, until I close all Seamonkey instances while
trying to fix the problem.

What happens then is Seamonkey pops up a box that complains it is
already running, and to close that Seamonkey before trying to run.

But there are no visible instances of Seamonkey running.

Going to the Task Manager, I see an instance of Seamonkey IS running. So
I kill it in Task Manager.
Then I kill it again.
Then I kill it again ... etc. etc.

The Seamonkey process is unkillable.

I have to at this point re-boot before the browser starts working again.

What can I do to help get this fixed? There is no crash report because
Seamonkey is unaware it's munged and unreachable.

Help!



I've seen something like this also and have not yet a solution. One
suggestion is to update to Win XP SP3 then reinstall SM.


How do you update to XP SP3 when you have Vista SP2 ?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-02-08 Thread P.N.

Hello Pat,

I've installed SM 2.0.2 on the laptop of my daughter (running vista) - 
works without problems. However, the site You've used might contain some 
suspicious IE-only code or even VBScript, so please add some info here 
about the URLs to look at for testing or use Help-Report Broke Web 
Site


Kind regards

P.



Pat Welch wrote:

Hi.

This has gotten to the point I'm going to have to abandon SM 2.x soon. I
never saw this in any 1.x version.

I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
Turion dual-core chip, 3 MB RAM.

After about 8 hours of use, suddenly the browser stops working in a
curious way - clicking on a bookmark or an embedded URL silently
presents a blank page, no complaints, just no pages will display.

Email continues to work, until I close all Seamonkey instances while
trying to fix the problem.

What happens then is Seamonkey pops up a box that complains it is
already running, and to close that Seamonkey before trying to run.

But there are no visible instances of Seamonkey running.

Going to the Task Manager, I see an instance of Seamonkey IS running. So
I kill it in Task Manager.
Then I kill it again.
Then I kill it again ... etc. etc.

The Seamonkey process is unkillable.

I have to at this point re-boot before the browser starts working again.

What can I do to help get this fixed? There is no crash report because
Seamonkey is unaware it's munged and unreachable.

Help!



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


Re: 2.0.2 in Vista - the browser crashes silently, leaving an unkillable process that prevents running Seamonkey.

2010-02-08 Thread Pat Welch

P.N. wrote:

Hello Pat,

I've installed SM 2.0.2 on the laptop of my daughter (running vista) -
works without problems. However, the site You've used might contain some
suspicious IE-only code or even VBScript, so please add some info here
about the URLs to look at for testing or use Help-Report Broke Web
Site

Kind regards

P.



Pat Welch wrote:

Hi.

This has gotten to the point I'm going to have to abandon SM 2.x soon. I
never saw this in any 1.x version.

I'm on 32-bit Windows Vista SP2 running on an HP notebook with the AMD
Turion dual-core chip, 3 MB RAM.

After about 8 hours of use, suddenly the browser stops working in a
curious way - clicking on a bookmark or an embedded URL silently
presents a blank page, no complaints, just no pages will display.

Email continues to work, until I close all Seamonkey instances while
trying to fix the problem.

What happens then is Seamonkey pops up a box that complains it is
already running, and to close that Seamonkey before trying to run.

But there are no visible instances of Seamonkey running.

Going to the Task Manager, I see an instance of Seamonkey IS running. So
I kill it in Task Manager.
Then I kill it again.
Then I kill it again ... etc. etc.

The Seamonkey process is unkillable.

I have to at this point re-boot before the browser starts working again.

What can I do to help get this fixed? There is no crash report because
Seamonkey is unaware it's munged and unreachable.

Help!





It's NOT a URL, because it happens on web sites I visit all the time, 
and not the same ones either.


As I said - it's after Seamonkey has been up and online for about 8 
hours or so. Memory leak anyone? :)


And whats up with the totally UNkillable 'ghost' copy of Seamonkey? Task 
Manager can not kill it no matter how many times I try, and there are no 
'visible' instances of SM open on the desktop.


The unkillable copy of SM is a deal breaker for me - I don't care WHAT 
caused the unkillable copy - the release copy of SM should never get in 
that state. Having to re-boot because of a misbehaving application is so 
1990's ...


--

Pat Welch, UBB Computer Services, a WCS Affiliate
   SCO Authorized Partner
   Microlite BackupEdge Certified Reseller
   Unix/Linux/Windows/Hardware Sales/Support
   (209) 745-1401 Cell: (209) 251-9120
   E-mail: pat...@inreach.com

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