Reply to thread

Message

<blockquote data-quote="Stopspying" data-source="post: 1013121" data-attributes="member: 69368">FF v107.0.1 crashed during the update, I had some open tabs and allowed the update while browsing them, intending to restart FF when the install was completed. It crashed again after a few minutes after opening FF again. I&#039;d checked if the update was completed, it was. Starting FF again it worked for about 5 minutes and then froze, memory usage went through the roof and the PC then froze, there is 32Gbs of RAM. I left the PC to see if it would revert back to normal, it did after a few minutes but FF had crashed again.This may be related toas I&#039;d noticed the same higher usage by FF when compared to LW. Or it could be a conflict with an extension, I have not installed any new ones recently, so it might be an updated extension conflicting, but I sense its more likely to be FF. I can&#039;t see any obvious extension conflict. The FF profile I was using has the latest Arkenfox user.js plus some other about:config tweaks. I opened a FF profile with no about:config tweaks and very few extensions, it seems to be stable. I&#039;ll report back if I narrow the cause down.<h2>Edit - I thought I should add that I was not doing anything else other than browsing at the time this was occuring, no intensive graphics tasks etc were taking place.</h2></blockquote>

[QUOTE="Stopspying, post: 1013121, member: 69368"] FF v107.0.1 crashed during the update, I had some open tabs and allowed the update while browsing them, intending to restart FF when the install was completed. It crashed again after a few minutes after opening FF again. I'd checked if the update was completed, it was. Starting FF again it worked for about 5 minutes and then froze, memory usage went through the roof and the PC then froze, there is 32Gbs of RAM. I left the PC to see if it would revert back to normal, it did after a few minutes but FF had crashed again. This may be related to as I'd noticed the same higher usage by FF when compared to LW. Or it could be a conflict with an extension, I have not installed any new ones recently, so it might be an updated extension conflicting, but I sense its more likely to be FF. I can't see any obvious extension conflict. The FF profile I was using has the latest Arkenfox user.js plus some other about:config tweaks. I opened a FF profile with no about:config tweaks and very few extensions, it seems to be stable. I'll report back if I narrow the cause down. [HEADING=1][SIZE=4][B]Edit - I thought I should add that I was not doing anything else other than browsing at the time this was occuring, no intensive graphics tasks etc were taking place.[/B][/SIZE][/HEADING] [/QUOTE]

Verification