Crash at machine save time. (Log attached)

[ci-zephyurus]

When I tried to save the virtual machine status in order to shutdown the host OS, VBox crashed saying an address very much near 0x000...000 could not be writen into. (I think it was 0xCB or something. Sorry I failed to capture the screen dump. Well, looking at the log, I think the address could be the value in ExceptionInformation[1]=00000000000000c8 )

I am attaching the VBox.log.2 file. The beginning of error stack dump is as follows:

135:21:02.909608 
135:21:02.909610 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000003d30 in 10396 !!!
135:21:02.909629 
135:21:02.909629 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffc1524eca0
135:21:02.909635 ExceptionInformation[0]=0000000000000001
135:21:02.909640 ExceptionInformation[1]=00000000000000c8
135:21:02.909645 
135:21:02.909645 cs:rip=0033:00007ffc1524eca0
135:21:02.909650 ss:rsp=002b:000000c83a6ff558 rbp=0000000000000000
135:21:02.909655 rax=00007ffc1524eca0 rcx=000002770ecc21e0 rdx=0000000000000000 rbx=000002770d2ea5c0
135:21:02.909661 rsi=0000000000000000 rdi=0000000000000000 rsp=000000c83a6ff558 rbp=0000000000000000
135:21:02.909666 r8 =0000000000000000 r9 =0000000000000001 r10=00000fff82a49d94 r11=0000000000101000
135:21:02.909671 r12=000002770ec4fd20 r13=0000000000000000 r14=000002770eb7d490 r15=000002771dde0180
135:21:02.909676 ds=002b es=002b fs=0053 gs=002b eflags=00010247
135:21:02.909681 p1home=0000000000000000 p2home=8000000000000007 pe3home=000002770d2ea5c0
135:21:02.909686 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
135:21:02.909691    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
135:21:02.909695 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000

I had to zip the log file. It was more than 700KB long and exceeded the file size limit.

[galitsyn]

Duplicate of #21711.

[ci-zephyurus]

The similar error happened when I tried to logout and login to guest linux, suggesting maybe the graphics display adapter implementation may have an issue.

I had updated VirtualBox to 7.0.8 on May 9.

It is possible I had failed to re-install the guest utility, esp. display driver. I have updated the display driver by running VBoxLinuxAdditions.run

So far a few times of logging-in/logging-out have not reproduced the error. I will monitor it and report any follow-up. Luckily, due to a font server issue, I will be restarting X server quite often in the next few days, and so display driver will go through quite a few times of initialization, shutdown, etc. So if the problem still persists, it will be quite likely to be caught.

Thank you in advance for people's attention.

[ci-zephyurus]

Interesting, I excerpted the failure stack portion from the Vbox.log.1 and renamed it as failed-vbox.log.1.txt, I could upload it.

Maybe the server tries to do something funny with .zip extension?

Anyway, the topmost part of the failure is the same as previously. The VBox code failes to handle certain exception.

******************** End of statistics **********************
47:00:43.971430 
47:00:43.971431 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 00000000000111ec in 35432 !!!
47:00:43.971446 
47:00:43.971446 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007fff681beca0
47:00:43.971452 ExceptionInformation[0]=0000000000000001
47:00:43.971456 ExceptionInformation[1]=00000000000000c8
47:00:43.971460 
47:00:43.971461 cs:rip=0033:00007fff681beca0
47:00:43.971466 ss:rsp=002b:000000fdaedff4d8 rbp=0000000000000000
47:00:43.971471 rax=00007fff681beca0 rcx=0000023a09af81c0 rdx=0000000000000000 rbx=0000023a08b016b0
47:00:43.971475 rsi=0000000000000000 rdi=0000000000000000 rsp=000000fdaedff4d8 rbp=0000000000000000
47:00:43.971480 r8 =0000000000000000 r9 =0000000000000001 r10=00000fffed037d94 r11=0000000000101000
47:00:43.971485 r12=0000023a09842af0 r13=0000000000000000 r14=0000023a08b98fb0 r15=0000023a14bd0180
47:00:43.971490 ds=002b es=002b fs=0053 gs=002b eflags=00010247
47:00:43.971494 p1home=0000000000000000 p2home=8000000000000007 pe3home=0000023a08b016b0
47:00:43.971499 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
47:00:43.971503    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
47:00:43.971508 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
47:00:43.971513 
47:00:43.971513 Stack 000000fdaedfe450, dumping 0x1bb0 bytes (low=000000fdaed00000, high=000000fdaee00000)
47:00:43.971519 000000fdaedfe450/0000: 73 74 61 63 6b 6d 61 72-6b 65 72 00 00 00 00 00 stackmarker.....
47:00:43.971521 000000fdaedfe460/0010: 00 10 00 00 20 00 00 00-00 00 00 01 00 00 00 00 .... ...........

I believe the address that caused the exception (memory violation?) was 00000000000000c8. I think something tries to access the memory address by ptr->member_at_offset_0xc8 and ptr was 0 (nullptr).