VirtualBox

Opened 3 months ago

Last modified 3 months ago

#22166 new defect

Virtualbox crash after using "vm activity overview"

Reported by: denture5688 Owned by:
Component: GUI Version: VirtualBox-7.1.0
Keywords: Cc: denture5688
Guest type: Windows Host type: Windows

Description (last modified by denture5688)

Hello,

When you go to File > Tools > VM Activity Overview on VBox home page, the application crash, and it cannot be reloaded.

I tried to uninstall the app but it still don't want to open. The only way i found to restart the app was to delete the following folder : C:\Users\REDACTED\.VirtualBox

I tried on multiple plateforms and the same bug happen. However, if they are already VMs created, the panel is displayed normally. I think this bug only happen if you have no VMs at all.

In C:\Users\REDACTED\.VirtualBox\selectorwindow.log, I have this : https://pastebin.com/YfC4b6hy

Tried on :

  • Windows 10 22H2 (10.0.19045) x64
  • Windows 11 22H2 (10.0.22621) x64
  • ArchLinux with Linux 6.10.9 and Gnome 46 x64

Change History (6)

comment:1 by denture5688, 3 months ago

Description: modified (diff)

comment:2 by denture5688, 3 months ago

Description: modified (diff)

comment:3 by denture5688, 3 months ago

Description: modified (diff)

comment:4 by denture5688, 3 months ago

Description: modified (diff)

comment:5 by alexvirtual, 3 months ago

Same result on Windows 10 22H2 (10.0.19045) x64.

To start it again, I have to task manager , remove the 2 processes, remove the preference file, and start again.

There is a post in the forums that seems to be related to the fact that if there is no vm's it will crash https://forums.virtualbox.org/viewtopic.php?t=112324

comment:6 by gombara, 3 months ago

Hello. I am able to reproduce this crash. It happens when there is no registered VM yet and user selects activity overview widget. Restarting the GUI does not help much since the last selected widget is remembered, thus crash again. One tentative solution is to create and register a dummy vm so that crasing code path is not triggered. You can use this command:

VBoxManage createvm --name=dummy321 --register

The problem itself is already fixed in the code base and will be available with the next release. Thanks a lot for reporting.

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