VirtualBox

Opened 13 years ago

Closed 10 years ago

#9194 closed defect (fixed)

VirtualBox core on loging after a long period of time => Fixed in SVN

Reported by: Gbillou Owned by:
Component: other Version: VirtualBox 4.1.6
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by Frank Mehnert)

When I leave my computer on a virtual terminal, then switch back to my X server a long time later (don't know exactly but something like an hour), then login (because my workstation is locked) i find my VirtualBox session stopped and its state is "aborted". All other software are still running fine.

Change History (12)

comment:1 by misha, 13 years ago

Did your guest have some mode switch (i.e. seamless<->windowed<->fullscreen) before the crash?

comment:2 by Gbillou, 13 years ago

Yes, i always run this vm in fullscreen mode but sometimes go to windowed mode to connect an usb key or else (i did hide the mini toolbar) Do you Wang me to try something?

comment:3 by misha, 13 years ago

So far I'm just trying to get the clue on how the VM process came to that broken state.. Could you specify in more detail steps you take to reproduce this, i.e.

  1. what guest you were running and were there any video or other sw using DDraw running in guest?
  2. were the VM running in a full screen mode when you switched off the X terminal
  3. did the VM crash already by the time you return back to X terminal? if not, were it still in the same mode (i.e. fullscreen?) ..just when you return? ..when it crashed?

comment:4 by Gbillou, 13 years ago

  1. I was running Windows Xp SP3 with guest addition 4.0.4 r70112. I did not try to run another guest. There were no directdraw application running. But i had run Acrobat Reader X, with a strange behavior when scrolling on pdf files. BTW it was not running while the vm crashed. Hmm, i'm not sure but maybe google chrome was running.. and so it might be using canvas or displaying a pdf file (not sure if it uses DDraw or not).
  2. yes
  3. yes, did crash already. I should have checked with VBoxManage from a VT if it did crash before going back to my X session. But yet i don't know. I'll try to check it next time i come back to my workstation and before going back to my X session.

I'm not able to reproduce it all time. I though so until today, as I leaved my computer on a vt, with as usal my win xp guest running on my X session. But when I came back let's say 1h30 later, the guest was still running (i found i "weird" thus it's the expected behavior :p)

comment:5 by Frank Mehnert, 12 years ago

Version: VirtualBox 4.0.10VirtualBox 4.1.6

We've got some more core dumps. We are trying to fix the problem but we still don't fully understand the problem.

comment:6 by kerlerm, 12 years ago

Problem persists with version 4.1.8 installed. Guests get aborted randomly.

comment:7 by Frank Mehnert, 12 years ago

Description: modified (diff)

Still relevant with VBox 4.1.22?

comment:8 by Frank Mehnert, 11 years ago

Resolution: fixed
Status: newclosed

No response, closing.

comment:9 by Frank Mehnert, 11 years ago

Resolution: fixed
Status: closedreopened

comment:10 by Frank Mehnert, 11 years ago

User qu3sti0n on IRC has the same problem with VBox 4.2.18 on Ubuntu 12.04 (Precise Pangolin). We already got the core dump.

comment:11 by Frank Mehnert, 10 years ago

Summary: VirtualBox core on loging after a long period of timeVirtualBox core on loging after a long period of time => Fixed in SVN

Finally we think we fixed this problem. The next 4.3.x maintenance release should contain the fix.

comment:12 by Frank Mehnert, 10 years ago

Resolution: fixed
Status: reopenedclosed

Should be finally fixed in 4.3.4.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use