it is not sufficient to throw hands up and say you can't re-create the error. If this is in fact what is happening, then it's clearly a coding error and needs to be fixed. Killing the process and then restarting FF solves the problem, which again seems reasonable if my conjecture is right. It seems reasonable to surmise that when FF crashes, the communication is lost and enpassNVhost runs around like a headless chicken, out of control and not knowing what to do but desperately searching for the FF add-on. This is conjecture, but according to my understanding, NVhost is communications code, I assume it bridges between the FF add-on and the enpass app. Immediately after than, enpassNVhost grabs ober 100% of cpu and horrible overheating starts to happen. It happens when Firefox crashes for whatever reason, and I do not exclude that Enpass is crashing it. Like others, I have had this problem (previously posted).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |