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.

[ci-zephyurus]

Strange. I cannot upload the log file

• Original: probably too large.
• zipped file: still the same error message.

Request Entity Too Large The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.

I tried to split the log file into two. Both of them are smaller files (280K, 480 KB).

Still NO GO. The same error message.

Something is wrong with the new bug reporting system. (I say new because it o=looks a bit different from the screen image I recall a month or so ago.)

I can send the file by e-mail. :-(

[ci-zephyurus]

I tried both Firefox and Google chrome browser. Let me see if MS Edge works here.

[ci-zephyurus]

VBox.log.1.zip but with .txt suffix attached. This *IS* a zipped file.

[ci-zephyurus]

I got the same crash while running a program. (Not save time) The topmost crash dump is as follows. Almost the same. Stack pointer is different, but the program counter seems to point at the same place.

137:48:19.501835 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000090c in 35980 !!!
137:48:19.501973 
137:48:19.501973 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ffdc53aeca0
137:48:19.501981 ExceptionInformation[0]=0000000000000001
137:48:19.501987 ExceptionInformation[1]=00000000000000c8
137:48:19.501992 
137:48:19.501992 cs:rip=0033:00007ffdc53aeca0
137:48:19.502000 ss:rsp=002b:0000001e887ff478 rbp=0000000000000000
137:48:19.502006 rax=00007ffdc53aeca0 rcx=000001d71041e200 rdx=0000000000000000 rbx=000001d711c8e8d0
137:48:19.502012 rsi=0000000000000000 rdi=0000000000000000 rsp=0000001e887ff478 rbp=0000000000000000
137:48:19.502018 r8 =0000000000000000 r9 =0000000000000001 r10=00000fffb8a75d94 r11=0000000000101000
137:48:19.502026 r12=000001d7111aeae0 r13=0000000000000000 r14=000001d710e66f60 r15=000001d71c680180
137:48:19.502038 ds=002b es=002b fs=0053 gs=002b eflags=00010247
137:48:19.502046 p1home=0000000000000000 p2home=8000000000000007 pe3home=000001d711c8e8d0
137:48:19.502051 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
137:48:19.502056    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
137:48:19.502061 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
137:48:19.502070 

VBox version is 7.0.8 r156879 (Qt5.15.2)

I have tried to upload the zipped log file but still no go. But given the strange behavior of the webserver I have observed, I have an idea. I created a zipped VBox.log.1.zip, but attach a filename suffix ".txt" to fool whatever is interfering the upload of raw log file or zipped log file. I wonder if it works. YES, IT WORKED. Strange.

[ci-zephyurus]

Looks like a problem in display related code.

137:48:19.503514 Potential code addresses on the stack:
137:48:19.503519 Xcpt PC         : 00007ffdc53aeca0 - 0x0012eca0 bytes into C:\WINDOWS\SYSTEM32\d3d11.dll
137:48:19.503525 0000001e887ff478: 00007ffccf483843 - 0x000d3843 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
137:48:19.503531 0000001e887ff488: 00007ffccffda771 - 0x0008a771 bytes into C:\Program Files\Oracle\VirtualBox\VBoxVMM.DLL
137:48:19.503537 0000001e887ff4b8: 00007ffccf486f47 - 0x000d6f47 bytes into C:\Program Files\Oracle\VirtualBox\VBoxDD.DLL
   ... omission ...

[ci-zephyurus]

Another crash at the satus save time. Host Windows 10, guest Debian GNU/Linux.

The attached file, 2023-07-14-crash-VBox.zip.txt​, actually is NOT a text file. It is a zip file of the VBox.log when the crash occurs. Somehow I cannot upload .zip file to the bugtracker. Simply renameit to 2023-07-14-crash-VBox.zip and unzip it to obtain the log.

Again, the crash had the same signature as before.

540:16:43.901974 
540:16:43.901975 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000008214 in 50900 !!!
540:16:43.901993 
540:16:43.901993 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ff99c35eca0
540:16:43.901998 ExceptionInformation[0]=0000000000000001
540:16:43.902003 ExceptionInformation[1]=00000000000000c8
540:16:43.902007 
540:16:43.902008 cs:rip=0033:00007ff99c35eca0
540:16:43.902013 ss:rsp=002b:00000066644ff998 rbp=0000000000000000
540:16:43.902018 rax=00007ff99c35eca0 rcx=000001fbbc341350 rdx=0000000000000000 rbx=000001fbb76f88b0
540:16:43.902023 rsi=0000000000000000 rdi=0000000000000000 rsp=00000066644ff998 rbp=0000000000000000
540:16:43.902028 r8 =0000000000000000 r9 =0000000000000001 r10=00000fff3386bd94 r11=0000000000101000
540:16:43.902033 r12=000001fbbb9b0990 r13=0000000000000000 r14=000001fbba928430 r15=000001fbc9010180
540:16:43.902037 ds=002b es=002b fs=0053 gs=002b eflags=00010247
540:16:43.902042 p1home=0000000000000000 p2home=8000000000000007 pe3home=000001fbb76f88b0
540:16:43.902047 p4home=0000000000000000 p5home=0000000000000000 pe6home=0000000000000000
540:16:43.902051    LastBranchToRip=0000000000000000    LastBranchFromRip=0000000000000000
540:16:43.902056 LastExceptionToRip=0000000000000000 LastExceptionFromRip=0000000000000000
540:16:43.902062 

With the same problematic 00000000000000c8 address. I think it is a symptom freed and nulled pointer is used to access a member at off 0xc8. ptr->something (where ptr is null).

In any case, the "rtR3WinUnhandledXcptFilter" is the culprit IMHO.

[ci-zephyurus]

In any case, the "rtR3WinUnhandledXcptFilter" is the culprit IMHO.

Of course, that is the exception reporter. The real culprit is

540:16:43.903294 Potential code addresses on the stack:
540:16:43.903298 Xcpt PC         : 00007ff99c35eca0 - 0x0012eca0 bytes into C:\WINDOWS\SYSTEM32\d3d11.dll

I will try disabling 3D acceleration and see if that helps.