Opened 11 months ago
Last modified 11 months ago
#22020 new defect
Taking a screenshot with Greenshot crashes VM on VBox 7.0
Reported by: | john vc | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox-7.0.14 |
Keywords: | Greenshot, Screenshot, crash, snipping tool | Cc: | John, vc |
Guest type: | Linux | Host type: | Windows |
Description
Hi all,
first of all I'm aware that this issue has been already mentioned in another issue in the past: viewtopic.php?p=333061 and that there is also a bug report for that #14447 but both are almost 10 years old and that is why I decided to post a new one here.
Also I created an issue in the VirtualBox Forum, with the same information. I was told I should create a bug in here, and so am I doing. https://forums.virtualbox.org/viewtopic.php?t=111213
Despite of navigating through the VirtualBox Forum for quite a while, this is my first post. I apologise in advanced if I have skipped some required information or missunderstood the rules of the forum.
Issue Description: When using Greenshot to take a screenshot on my Host (Windows), usually it crashes my VM. An error message appears. If I first do a backup or shutdown the VM safely, that process never ends so that I finally have to click on the OK and the VM crashes anyway.
Error message: VirtualBoxVM.exe - Error in application The instruction in 0x00007FFF773B161E referred to memory at 0x00000021A10864000. The read operation could not be performed in memory. Click on "OK" to end the program. NOTE: the error message was translated into English, i.e. it may not be exactly the same wording if my OS was in English.
Version Info of VM: VirtualBox 7.0 VirtualBox VM 7.0.14 r161095 win.amd64 (Qt5.15.2) OS Host: Edition: Windows 10 Enterprise Version: 22H2 Build: 19045.4046 Windows Feature Experience Pack 1000.19053.1000.0 OS Guest: Ubuntu 233.04 64-bit Kernel Version: Linux 6.2.0.39-generic
From VirtualBox Log:
00:00:02.358995 VirtualBox VM 7.0.14 r161095 win.amd64 (Jan 15 2024 14:59:30) release log
00:00:02.358996 Log opened 2024-03-04T15:09:31.098220000Z
00:00:02.358996 Build Type: release
00:00:02.358999 OS Product: Windows 10
00:00:02.358999 OS Release: 10.0.19045
00:00:02.359000 OS Service Pack:
00:00:02.422217 DMI Product Name: System Product Name
00:00:02.424589 DMI Product Version: System Version
00:00:02.424593 Firmware type: UEFI
00:00:02.424978 Secure Boot: VERR_PRIVILEGE_NOT_HELD
00:00:02.424990 Host RAM: 64729MB (63.2GB) total, 50905MB (49.7GB) available
00:00:02.424991 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe
00:00:02.424992 Process ID: 38064
00:00:02.424992 Package type: WINDOWS_64BITS_GENERIC
00:00:02.425316 Installed Extension Packs:
00:00:02.425325 Oracle VM VirtualBox Extension Pack (Version: 7.0.12 r159484; VRDE Module: VBoxVRDP; Crypto Module: VBoxPuelCrypto)
Attached you'll find my Logs folder as ZIP file.
thanks, John
PD: after posting this issue and bug, I've updated the Extension Pack to 7.0.14.
Attachments (1)
Change History (5)
by , 11 months ago
follow-ups: 2 4 comment:1 by , 11 months ago
comment:2 by , 11 months ago
Replying to fth0:
FWIW, the crashes happened in the Shared Clipboard thread.
Do you mean I should move this ticket to the shared Clipboard thread?
comment:3 by , 11 months ago
It was just meant as a hint for the VirtualBox devs. Since I know that the Shared Clipboard is regularly being worked on, it might increase the likelihood of this ticket being investigated.
FWIW, the crashes happened in the Shared Clipboard thread.