VirtualBox

Opened 5 years ago

Last modified 5 years ago

#18390 new defect

'memory could not be read' crash in Linux guest / Windows host 6.02 and 6.04

Reported by: MattA Owned by:
Component: other Version: VirtualBox 6.0.4
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

I am running a Linux guest (Mint Virtualbox image downloaded from www.osboxes.org) in a Windows 10 host.

I started running this guest under VirtualBox 6.0.2 and experienced this crash. A couple of days later I noticed 6.0.4 was available and tried updating to that to see whether it had been fixed, but the crash is still occurring and has happened 3x today, so it is fairly regular.

The guest isn't running too much - it's being used as a dev box with Docker (postgres / pgAdmin) and VS Code. There doesn't seem to be a particular pattern in what I'm doing before a crash. The VM doesn't have many modifications to base settings - 2 CPU, bidir clipboard and 2 networks (NAT and Host Only).

The error message is: 'The instruction at 0x00007FFC612061E3 referenced memory at 0x00000000000010. The memory could not be read'

I have attached the output from VBoxBugReport

Attachments (1)

2019-01-30-17-20-38-bugreport.tgz (310.0 KB ) - added by MattA 5 years ago.
VBoxBugReport

Download all attachments as: .zip

Change History (5)

by MattA, 5 years ago

VBoxBugReport

comment:1 by Nicolas, 5 years ago

I have a similar error and can reproduce it in the following way:

  1. Set a breakpoint in Visual Studio Code
  2. Right click the breakpoint 2 times

Note: when right clicking the breakpoint for the first time, I get a black tooltip.

  • Host: Windows 10
  • Guest: Linux Mint 18.3 (Kernel 4.15.0-47)
  • VS Code: 1.33.0

The error message is slightly different for me: The instruction at 0x00007FFB3278E41C referenced memory at 0x00000000000000. The memory could not be written.


Update 2019-04-12:

I just noticed, that the same error occurs when right clicking two times on a method name in VS Code when debugging. There also a black tooltip/overlay window/context menu (I cannot tell) appears, when doing the first right click.

So, this has nothing to do with breakpoints, it is about this black thing.


Update 2019-04-12 - 2:

After noticing, that ALL menus in VS Code were black, I searched for a solution and found one: launching VS Code with the --disable-gpu switch

This means, my crash has something to do with the GPU access. I am using the "VMSVGA" controller. I tried the other two options, but they didn't work. The hardware is a Lenovo T540p with Intel HD Graphics 4600 (via Core i5-4300M) and NVIDIA GeForce GT 730M. I don't know which one of them is used and when.

Last edited 5 years ago by Nicolas (previous) (diff)

comment:2 by Trent Zhou, 5 years ago

I met the same problem. Thanks for pointing out the --disable-gpu option. It seems working.

comment:3 by Yoghoo, 5 years ago

Since upgrading to 6.0.8 my guest is crashing often as well with this error. Host is Windows 10 (build 1903) and guest is Ubuntu 18.04 LTS. If it happens (which is around half of the times) it happens when starting VLC to play a movie. Not using VS Code as mentioned above btw. Tried to change some graphic settings of the guest without solving this error unfortunately. If you need more info let me know.

comment:4 by Aren Cambre, 5 years ago

#18859 may be related?

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use