VirtualBox

Opened 4 years ago

Last modified 3 years ago

#20022 new defect

VM is causing Guest OS applications ( Slack/Intelli J ) hung

Reported by: Sandeep Reddy Owned by:
Component: host support Version: VirtualBox 6.1.16
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

I have windows machine with 32 Gigs RAM and core i7 with 8th Gen. I have installed Ubuntu inside my Oracle VM with 2 cores(Out of 8 Cores) and 8 Gigs RAM (Out of 32 Gigs RAM).

Guest OS application slack or IntelliJ works fine without any issues until I start the Ubuntu using Oracle VM 6.1

As soon I start my Ubuntu on my VM, slack and IntelliJ freezes for every 10 minutes and I need to wait for 2 to 3 minutes to respond and do my work, it became a routine for every 15 minutes.

Unfortunately I do not have any logs because I do not see any network/cpu/disk usage spike, when these applications get hung.

Change History (4)

comment:1 by jmval, 4 years ago

Hello,

I am facing a similar issue on a similar configuration:

  • Host with windows 10 64 bits - 16GB of RAM - core i7
  • Guest with Debian 9 - 3 cores - 8 GB of RAM

Not 100% sure, but I think that issue first appeared after installing Virtualbox 6.1.14.

What happens is when the VM is running, after a while (hard to define how long but let's say after 1 hour) my Slack windows desktop application starts freezing.

Once frozen, killing the Slack task and relaunching it does not help = slack displays a black screen. Sometimes Slack gets back functional after 2 to 3 minutes, sometimes it never does.

I recently noticed that Slack went systematically back functional after exiting the guest VM.

I also noticed yesterday that if I disable the screensaver inside the guest VM, the problem nearly disappears: Slack almost never gets frozen, and when it does it is stuck for a couple a seconds only.

Wanted to share this as a workaround for people facing a similar behavior

Regards,

Last edited 4 years ago by jmval (previous) (diff)

in reply to:  1 comment:2 by Stacy, 4 years ago

Hi jmval,

The workaround with disabling screensaver inside the guest VM helped me lot. Thanks!

Replying to jmval:

Hello,

I am facing a similar issue on a similar configuration:

  • Host with windows 10 64 bits - 16GB of RAM - core i7
  • Guest with Debian 9 - 3 cores - 8 GB of RAM

Not 100% sure, but I think that issue first appeared after installing Virtualbox 6.1.14.

What happens is when the VM is running, after a while (hard to define how long but let's say after 1 hour) my Slack windows desktop application starts freezing.

Once frozen, killing the Slack task and relaunching it does not help = slack displays a black screen. Sometimes Slack gets back functional after 2 to 3 minutes, sometimes it never does.

I recently noticed that Slack went systematically back functional after exiting the guest VM.

I also noticed yesterday that if I disable the screensaver inside the guest VM, the problem nearly disappears: Slack almost never gets frozen, and when it does it is stuck for a couple a seconds only.

Wanted to share this as a workaround for people facing a similar behavior

Regards,

comment:3 by Stacy, 4 years ago

I also saw the description of a similar issue on reddit: https://www.reddit.com/r/Slack/comments/gfcfse/slack_repeatedly_crashing_due_to_conflict_with/

On my machine the app hang report (the one Windows host generates) indeed contains the following:

Sig[0].Name=Application Name
Sig[0].Value=slack.exe
Sig[1].Name=Application Version
Sig[1].Value=4.12.2.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5fbc606b
Sig[3].Name=Hang Signature
Sig[3].Value=ba68
Sig[4].Name=Hang Type
Sig[4].Value=134217760
Sig[5].Name=Waiting on Application Name
Sig[5].Value=VirtualBoxVM.exe
Sig[6].Name=Waiting on Application Version
Sig[6].Value=6.1.16.40961

comment:4 by Dash, 3 years ago

I'm having the same issue.

Host = Core-i7, 32GB, Windows 10 Pro. VirtualBox 6.1.22. (But this has been a problem with earlier versions.)

Running a CentOS Linux Guest (configured with just 1 vCPU, 3GB RAM, NAT Network) appears to cause Slack to occasionally become unresponsive, in the way the OP described. If I kill the guest (but leave VirtualBox running), then Slack recovers and runs fine.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette