New consolidated response for email subscribers:
It should also be noted that while the Firefox task is up and running (before any process termination is performed manually) and the loop is being registered by Process Lasso, Firefox is useable (somewhat sluggish in scenario 1) and therefore I don't understand the conclusion that the loop is caused by a crashing process, ie. Firefox crashing.
That is because you are reporting an entirely different issue that looks the same (while accusing me of not acting for 2 years.. if only you knew how hard I work to keep Bitsum here).
We are going to keep an eye on Firefox and see if we can reproduce this, but this is the first report we've had, and haven't had a 'crashing software loop' report in many months, so it's unclear if that issue still exists.
As for confidence in Process Lasso, you should be supremely confident in it. BUT people are running extremely complex software ecosystems in their Windows installs, so it is hard to achieve 100% perfection in all scenarios just due to this software ecosystem complexity (e.g. the security software interoperability issue fix this week).
It would appear from your description that you have a something else going wrong on your PC. We have testers running Firefox constantly.
1. The PIDs you report as changing (on new launches).
2. Restarting Lasso doesn't fix the issue (clue that it's not Lasso)
3. I think you have a Firefox Extension that may be crashing ...
4. In any event, it is definitely *not* the 2 year old issue reported here, and I am still a little offended by the implication that I would rest of my laurels for 2 years if a critical bug did exist, and was known. I just work so hard, anyway... It's a late Sunday night, and I'm splitting this thread as it's a DIFFERENT issue.