From: Digest To: "OS/2GenAu Digest" Date: Sat, 10 Nov 2018 00:00:42 WST-8WST,10,1,0,7200,4,1,0,7200,0 Subject: [os2genau_digest] No. 2145 Reply-To: os2genau_digest at os2site.com X-List-Unsubscribe: www.os2site.com/list/ ************************************************** Friday 09 November 2018 Number 2145 ************************************************** Subjects for today 1 Re: Killing Firefox : 2 Re: Killing Firefox : Peter Moylan 3 Re: Killing Firefox : Peter Moylan 4 Re: Killing Firefox : 5 Re: Killing Firefox : Peter Moylan **= Email 1 ==========================** Date: Thu, 08 Nov 2018 19:39:18 +0100 From: Subject: Re: Killing Firefox On 8-11-18 02:03, Peter Moylan wrote: > Does anyone know which "kill" method TOP uses to kill a process? I'm > getting sick of having to hit Ctrl/Alt/Del twenty times a day whenever > Firefox has locked up the WPS, so I'm thinking of writing a utility that > would monitor Firefox and kill it whenever the Firefox CPU usage goes > above 99%. I guess you are using Firefox 45 ? That has a CPU hogging bug. Do you really want to kill Firefox ? It would mean any web forms opened would be toast ? > TOP itself is less suitable for this, because TOP can take literally > five minutes to start once Firefox is hogging 100% of the processor. What version are you running and what CPU are you using ? > Of course I could also go back to an earlier version of Firefox, and > just use Windows for sites (like internet banking) that insist on using > the bleeding edge features of browsers. That issue is under investigation and is known issue. It sounds like your system is somewhat underpowered ? Its a known issue but on my underpowered Dual HP laptop of six years old it does not take 5 minutes to load top. Sounds like extremely underpowered system. But I could be wrong. Roderick ----------------------------------------------- To Subscribe/Unsubscribe go to =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This is a pulp free product. **= Email 2 ==========================** Date: Fri, 9 Nov 2018 22:49:26 +1100 From: Peter Moylan Subject: Re: Killing Firefox On 08/11/18 23:15, majilok at gmail.com wrote: > Afraid I haven't been contributing much at all to all the OS/2-eCS > groups that I'm still subscribed to, and still reading, but am > awaiting cataract surgery (halfway into the 12 month waiting list > now) but do you have an Android/Samsung Smartphone or tablet? > > I do all my banking electronically to NAB using their excellent " app > ", & I only use the full-desktop version under Chrome when I get a > msg to tell me that latest VISA monthly statement is ready to > download, and ditto for my Flexi (Retirement/Pension) Savings > account, at 6 monthly intervals. One can place an online order for > Flexi a/c for a specific nominated period in addition to the standard > ones above. I have a similar app from my building society, but I use it only when travelling. It's pretty good, but I don't like dealing with such a small screen. It also has one feature that greatly annoys me: it lists transactions in reverse date order, and I don't naturally think backwards in time. The web interface has an option to change the order, but the phone app doesn't. One reason this matters to me is that I have my own program, which I wrote about 30 years ago, to keep track of all the household accounts. (So I can answer questions like "who repaired the washing machine five years ago?") My biggest use of on-line banking is to reconcile my records with the building society's, which among other things has been invaluable for detecting fraudulent credit card transactions. That's easy enough when I have two windows side-by-side on the same screen. Still, perhaps I could try propping up the phone against the screen. Sorry to hear about your health problems. Let's hope that this coming year is less complicated. -- Peter Moylan peter at pmoylan.org http://www.pmoylan.org The colour of a fireman's braces is entirely his own business. ----------------------------------------------- To Subscribe/Unsubscribe go to =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This is a pulp free product. **= Email 3 ==========================** Date: Fri, 9 Nov 2018 23:01:31 +1100 From: Peter Moylan Subject: Re: Killing Firefox On 09/11/18 05:39, roderickklein at xs4all.nl wrote: > On 8-11-18 02:03, Peter Moylan wrote: >> Does anyone know which "kill" method TOP uses to kill a process? >> I'm getting sick of having to hit Ctrl/Alt/Del twenty times a day >> whenever Firefox has locked up the WPS, so I'm thinking of writing >> a utility that would monitor Firefox and kill it whenever the >> Firefox CPU usage goes above 99%. > > I guess you are using Firefox 45 ? That has a CPU hogging bug. Yes, it's version 45.9.0. > Do you really want to kill Firefox ? It would mean any web forms > opened would be toast ? True, but I'm talking about the sort of emergency where the WPS is totally locked up and everything, including Firefox, is unresponsive. Under those conditions, the only available options are to kill Firefox or reboot the OS. If I reboot the OS I lose a lot more work, and of course that kills Firefox anyway. If I kill Firefox then all of my other running programs go back to normal responsiveness. >> TOP itself is less suitable for this, because TOP can take >> literally five minutes to start once Firefox is hogging 100% of >> the processor. > What version are you running and what CPU are you using ? TOP version 2.13. CPU is Intel Core 2 Duo 3 GHz. But perhaps I was unclear. Under normal conditions TOP responds immediately. It is only when Firefox is using 100% of the CPU, which it has been doing many times per day, that it takes minutes to get TOP (or any other program) to respond. -- Peter Moylan peter at pmoylan.org http://www.pmoylan.org The colour of a fireman's braces is entirely his own business. ----------------------------------------------- To Subscribe/Unsubscribe go to =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This is a pulp free product. **= Email 4 ==========================** Date: Fri, 09 Nov 2018 16:05:06 +0100 From: Subject: Re: Killing Firefox On 9-11-18 13:01, Peter Moylan wrote: > On 09/11/18 05:39, roderickklein at xs4all.nl wrote: >> On 8-11-18 02:03, Peter Moylan wrote: > >>> Does anyone know which "kill" method TOP uses to kill a process? >>> I'm getting sick of having to hit Ctrl/Alt/Del twenty times a day >>> whenever Firefox has locked up the WPS, so I'm thinking of writing >>> a utility that would monitor Firefox and kill it whenever the >>> Firefox CPU usage goes above 99%. >> >> I guess you are using Firefox 45 ? That has a CPU hogging bug. > > Yes, it's version 45.9.0. > >> Do you really want to kill Firefox ? It would mean any web forms >> opened would be toast ? > > True, but I'm talking about the sort of emergency where the WPS is > totally locked up and everything, including Firefox, is unresponsive. > Under those conditions, the only available options are to kill Firefox > or reboot the OS. If I reboot the OS I lose a lot more work, and of > course that kills Firefox anyway. If I kill Firefox then all of my other > running programs go back to normal responsiveness. You really need to describe in detail what happens on your system because I get the feeling two issue's might be occuring. The first is that in some cases Firefox can simply become a zombie process and you can not kill that instance of Firefox anymore. One question that comes to mind. When you press C-A-D is the menu shown where you can select TOP or restart the system instantly ? Or do you first get a Firefox screen that is graphical distorted with bar accross the screen. >>> TOP itself is less suitable for this, because TOP can take >>> literally five minutes to start once Firefox is hogging 100% of >>> the processor. > >> What version are you running and what CPU are you using ? > > TOP version 2.13. CPU is Intel Core 2 Duo 3 GHz. > > But perhaps I was unclear. Under normal conditions TOP responds > immediately. It is only when Firefox is using 100% of the CPU, which it > has been doing many times per day, that it takes minutes to get TOP (or > any other program) to respond. I am wondering if something else is going on in these cases where it takes that long to load TOP. Roderick ----------------------------------------------- To Subscribe/Unsubscribe go to =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This is a pulp free product. **= Email 5 ==========================** Date: Sat, 10 Nov 2018 02:24:54 +1100 From: Peter Moylan Subject: Re: Killing Firefox On 10/11/18 02:05, roderickklein at xs4all.nl wrote: > On 9-11-18 13:01, Peter Moylan wrote: >> On 09/11/18 05:39, roderickklein at xs4all.nl wrote: >>> On 8-11-18 02:03, Peter Moylan wrote: >> >>>> Does anyone know which "kill" method TOP uses to kill a >>>> process? I'm getting sick of having to hit Ctrl/Alt/Del twenty >>>> times a day whenever Firefox has locked up the WPS, so I'm >>>> thinking of writing a utility that would monitor Firefox and >>>> kill it whenever the Firefox CPU usage goes above 99%. >>> >>> I guess you are using Firefox 45 ? That has a CPU hogging bug. >> >> Yes, it's version 45.9.0. >> >>> Do you really want to kill Firefox ? It would mean any web forms >>> opened would be toast ? >> >> True, but I'm talking about the sort of emergency where the WPS is >> totally locked up and everything, including Firefox, is >> unresponsive. Under those conditions, the only available options >> are to kill Firefox or reboot the OS. If I reboot the OS I lose a >> lot more work, and of course that kills Firefox anyway. If I kill >> Firefox then all of my other running programs go back to normal >> responsiveness. > > You really need to describe in detail what happens on your system > because I get the feeling two issue's might be occuring. > > The first is that in some cases Firefox can simply become a zombie > process and you can not kill that instance of Firefox anymore. No, I can kill it with TOP. It's just that the TOP display of processes takes a while to appear. > One question that comes to mind. When you press C-A-D is the menu > shown where you can select TOP or restart the system instantly ? CAD produces the menu immediately. I can select TOP immediately, but then it takes TOP a while to produce its list of processes. > Or do you first get a Firefox screen that is graphical distorted > with bar accross the screen. No, that doesn't happen. > I am wondering if something else is going on in these cases where it > takes that long to load TOP. No, TOP loads immediately. The delay is before TOP is able to display the list of processes. I'm running MemSize all the time. The problem I'm describing is when MemSize reports more than 50% usage. (For some reason, MemSize only reports half the processor usage that TOP does.) At that point, the WPS is unable to receive any keyboard or mouse input. The only input that is recognised is Ctrl/Alt/Delete. This gives the CADH screen (with no delay). If I now choose TOP, the screen blanks, and then there is a long delay before TOP lists the processes. When the list finally appears, it shows that Firefox is currently using 100% of the processor. The average value is slightly lower than this. If I choose to kill Firefox at this point, the system returns to normal behaviour. -- Peter Moylan peter at pmoylan.org http://www.pmoylan.org The colour of a fireman's braces is entirely his own business. ----------------------------------------------- To Subscribe/Unsubscribe go to =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This is a pulp free product.