In both cases, I manually END-TASK'd all FF stubs, and in both cases, "ncolow" quit itself when the last FF was ended.
On the tower, seven or eight FF stubs and one "ncolow". On the laptop, Task Manager showed two FF stubs (typically about 2700 kb), with a single instance of "ncolow".
Specifically, Firefox and something called "ncolow", neither of which were obviously open. It so happens that a routine update of my Norton Security program needed to apply a patch on each machine and waited for certain programs to close on each. I recently encountered FF non-responses on two PC machines (tower and laptop, both running Windows 7), including today. (Then usually cancel the Windows search for solution because nothing comes up anyway.) Occasionally, if I wait long enough, FF might eventually respond, but usually, I end up with the standard Windows "close program" / "wait for respond" popup, and close the program. I don't recall that clearing history made any difference. For example, a click-bait sequence of pages invariably results in a hang, where closing and restarting FF resumes and continues for a few more pages before hanging again. And re-visit doesn't seem to make a difference - sometimes a hang, sometimes not. But there is no rhyme or reason to the hangs - just sometimes they happen, other times not. The problematic sites for me are generally news & info sites (known lots of Flash there), but also various garden-variety sites that don't obviously/prominently use Flash but of course might do so. I saw somewhere (don't recall where) during the recent buzz over Flash vulnerabilities that FF may (or does) disable Flash, and that this may cause problems certain Flash-dependent pages. I've had several strange "FF not responding" situations since FF 40, and I was hoping it was fixed in the newly installed FF 41.
0 kommentar(er)
