Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Seems to not play nicely with VBox. someone crashes depending on who is open first

  • 2 antwoorde
  • 0 hierdie probleem
  • 1 view
  • Laaste antwoord deur starsaa

starsaa
starsaa
more options

Right off the bat here - I get no error messages to read, but the crash log does get sent.

If I have Vbox open then FF may a hard time ether starting or staying running. If FF is running first then VBox may have a hard time starting. Many crash reports automatically submitted by FF Nightly. All SW is up to date. FF doesn't always crash as soon as I try and start it if VB is open and if it is already running it may randomly crash on me. As you can tell by my wording, it is totally random and frustrating! At times I will have to shut down FF in order to load my VB instance and sometimes it loads fine. And the opposite, if I have VB running sometimes I have to close it in order to get FF to load. The times that everything loads fine then FF usually crashes at some random point. I currently have 16 tabs split across 2 windows (seems to help it stay running) I have most of my extensions turned off. Even when I went down to just 1 default tab it did crash on me. With my 2 windows and 16 tabs FF task manager shows ~280MB memory, 15% CPU or less after I wait a few minutes for it to all load. Threads vary a lot but seemed to go around 23 out of 80. Windows task manager showed 590MB and 7% CPU. Even with this few tabs it will sometimes get up to 1GB or more of system memory according to windows, but CPU still stays single digits, maybe low teens. It started about the end of Nov when I installed VB. When I have VB and FF running Win task manager shows ~ half my memory free.

I hope this is all the info U need to help me out. BTW, if I'm reading the crash report right it says I'm getting an oom error? And it looks like its only supposed to happen with low memory, I still have 12GB free. Any JAVA packages should be up to date.

FF Nightly is kept up to date (usually no more than 2 days) currently 110.0a1 1-3-2023 64b Windows 10 Pro (also kept up to date) as well as all drivers AMD FX 8320 8 Core CPU 24 GB DDR3 and Windows, VB and FF are on my 500GB SSD (~50% used) VBox is Current and up to date 7.0.4r154605 Extension and Expansion packs are current and for this ver VB settings: 12GB Ram - 4 CPU - 80GB Drive (On my SSD) Those settings are half my memory and CPU.

Right off the bat here - I get no error messages to read, but the crash log does get sent. If I have Vbox open then FF may a hard time ether starting or staying running. If FF is running first then VBox may have a hard time starting. Many crash reports automatically submitted by FF Nightly. All SW is up to date. FF doesn't always crash as soon as I try and start it if VB is open and if it is already running it may randomly crash on me. As you can tell by my wording, it is totally random and frustrating! At times I will have to shut down FF in order to load my VB instance and sometimes it loads fine. And the opposite, if I have VB running sometimes I have to close it in order to get FF to load. The times that everything loads fine then FF usually crashes at some random point. I currently have 16 tabs split across 2 windows (seems to help it stay running) I have most of my extensions turned off. Even when I went down to just 1 default tab it did crash on me. With my 2 windows and 16 tabs FF task manager shows ~280MB memory, 15% CPU or less after I wait a few minutes for it to all load. Threads vary a lot but seemed to go around 23 out of 80. Windows task manager showed 590MB and 7% CPU. Even with this few tabs it will sometimes get up to 1GB or more of system memory according to windows, but CPU still stays single digits, maybe low teens. It started about the end of Nov when I installed VB. When I have VB and FF running Win task manager shows ~ half my memory free. I hope this is all the info U need to help me out. BTW, if I'm reading the crash report right it says I'm getting an oom error? And it looks like its only supposed to happen with low memory, I still have 12GB free. Any JAVA packages should be up to date. FF Nightly is kept up to date (usually no more than 2 days) currently 110.0a1 1-3-2023 64b Windows 10 Pro (also kept up to date) as well as all drivers AMD FX 8320 8 Core CPU 24 GB DDR3 and Windows, VB and FF are on my 500GB SSD (~50% used) VBox is Current and up to date 7.0.4r154605 Extension and Expansion packs are current and for this ver VB settings: 12GB Ram - 4 CPU - 80GB Drive (On my SSD) Those settings are half my memory and CPU.

All Replies (2)

techguy150
techguy150
more options

Had exactly the same problem since last week, just with Win 8.1 and Workstation 10 (which was running without problems for the last 5 years).

- Re-Installed Workstation --> nothing changed.

- Bought 2 new RAM (thought it might be at an end after 8 years) --> nothing changed.

Today I deactivated AVG on the host-computer and since then everything is fine again (at least until now - since 2,5 hours)

Would be interested if you are running AVG as well

starsaa
starsaa Vraag-eienaar
more options

I'm not. I was using IOBit but changed. Made no difference. Currently Just Windows Defender. Im not sure yet what I will replace it with. BTW, my VB did crash yesterday evening while I was using FF. But FF did stay running! Time for Nightlys update, lets see what happens.....

Gewysig op deur starsaa