Opened 4 years ago
Last modified 4 years ago
#19071 reopened defect
W10 Guest crash when watching youtube videos
| Reported by: | Pablo Sanchez | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
Hi,
When I found 6.0.14 crashing, I tested with the latest nightly[1] and Extension[1.5].
My Host O/S is openSUSE Tumbleweed. I am up to date[2].
The Guest O/S is an up to date W10 VM.
While watching a youtube video (any will do), the VM crashes.
The following errors are logged. First, in /var/log/messages:
Nov 7 17:05:08 fuzzy kernel: EMT-1[28979]: segfault at 7fe0ee42d920 ip 00007fe21dd295ff sp 00007fe1ee42d898 error 4 in libc-2.30.so[7fe21dca6000+14d000] Nov 7 17:05:08 fuzzy kernel: Code: a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6 0e 88 0f c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
after, in VBoxSVC.log:
00:07:50.279667 main Saving settings file "/home/xyz/.VirtualBox/load_test/load_test.vbox" with version "1.15-linux"
00:07:50.742201 Watcher Reaper: Pid 28941 (710d) was signalled: 11 (0xb)
00:07:55.284290 main VirtualBox: object deletion starts
00:07:55.284327 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/w10/w10.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.284451 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/r-mobile/r-mobile.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.284533 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={ad47ad09-787b-44ab-b343-a082a3f2dfb1} aComponent={MediumWrap} aText={Medium '/home/xyz/.VirtualBox/load_test/load_test.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:07:55.743302 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:08:00.315967 main {00007ff38001ba80} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT
00:08:00.317272 main VirtualBox: object deleted
Nothing is placed in VBox.log
Please let me know what other data is needed. I am sure you need more. ;)
References 1 - VirtualBox-6.0.15-134477-Linux_amd64.run 1.5 - Oracle_VM_VirtualBox_Extension_Pack-6.0.15-134477.vbox-extpack 2 - Tumbleweed version 20191104
Attachments (1)
Change History (20)
comment:1 by , 4 years ago
| Status: | new → awaitsfeedback |
|---|
comment:2 by , 4 years ago
| Status: | awaitsfeedback → new |
|---|
comment:3 by , 4 years ago
Test Case
- Start chrome
- Watch the following Ellen .. ;) .... youtube video: https://www.youtube.com/watch?v=8kI8tnefeds
- After three to six minutes, the VM will crash. I haven't timed it or confirmed if it happens at the exact playback time. If required, I can do that.
follow-up: 10 comment:5 by , 4 years ago
I could not reproduce the crash. Please get a minidump from the guest:
comment:6 by , 4 years ago
Hi,
Unfortunately no minidump is created.
As before I noticed in /var/log/messages the following message when the VM crashed - see the segfault at line 1:
Nov 22 17:24:53 zoom kernel: EMT-1[13412]: segfault at 7fd363dfe920 ip 00007fd4968805ff sp 00007fd463dfe898 error 4 in libc-2.30.so[7fd4967fd000+14d000] Nov 22 17:24:53 zoom kernel: Code: a4 c3 80 fa 08 73 12 80 fa 04 73 1e 80 fa 01 77 26 72 05 0f b6 0e 88 0f c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66 Nov 22 17:24:53 zoom kwin_x11[2464]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 27849, resource id: 130023436, major code: 15 (QueryTree), minor code: 0 Nov 22 17:24:53 zoom kwin_x11[2464]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 27854, resource id: 130023436, major code: 18 (ChangeProperty), minor code: 0
Given the above, I generated a VirtualBox core dump following these instructions[1]. Without any debug symbols, it may be useless but perhaps it'll get us started.
gdb core
# gdb core
GNU gdb (GDB; openSUSE Tumbleweed) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
[New LWP 1419]
[New LWP 1421]
[New LWP 1394]
[New LWP 1423]
[New LWP 1415]
[New LWP 1432]
[New LWP 1396]
[New LWP 1436]
[New LWP 1395]
[New LWP 1831]
[New LWP 1397]
[New LWP 1404]
[New LWP 1584]
[New LWP 1398]
[New LWP 1430]
[New LWP 1399]
[New LWP 1426]
[New LWP 1485]
[New LWP 1400]
[New LWP 1418]
[New LWP 1427]
[New LWP 1403]
[New LWP 1429]
[New LWP 1391]
[New LWP 1425]
[New LWP 1420]
[New LWP 1431]
[New LWP 1424]
[New LWP 1422]
[New LWP 1435]
[New LWP 1428]
[New LWP 1434]
[New LWP 1433]
Missing separate debuginfo for the main executable file
Try: zypper install -C "debuginfo(build-id)=1c873334ccaa6b882c72f5289f99f62b308e65cb"
Core was generated by `/opt/VirtualBox/VirtualBoxVM --comment load_test --startvm 223dd16e-a2d0-48e7-8'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f6a923f15ff in ?? ()
[Current thread is 1 (LWP 1419)]
"/var/lib/systemd/coredump/core" is a core file.
Please specify an executable to debug.
(gdb) where
#0 0x00007f6a923f15ff in ?? ()
#1 0x00007f6a557607c7 in ?? ()
#2 0x000000968baf5833 in ?? ()
#3 0x00007f6a5e401e50 in ?? ()
#4 0x00007f6a802dfa2c in ?? ()
#5 0x0000000083776c39 in ?? ()
#6 0x00007f6a5e401d28 in ?? ()
#7 0x00007f6a5e400f80 in ?? ()
#8 0x00007f6a5e401df0 in ?? ()
#9 0x000000000000000c in ?? ()
#10 0x00000000802dfab0 in ?? ()
#11 0x0000010c00000000 in ?? ()
#12 0x00007f6a802df910 in ?? ()
#13 0x00007f6a802dfa18 in ?? ()
#14 0x00007f6a802dfa20 in ?? ()
#15 0x00007f6a0000000c in ?? ()
#16 0x001b0017ffff0000 in ?? ()
#17 0x00000000ffff0000 in ?? ()
#18 0xffff000000080003 in ?? ()
#19 0xffcbffc6ffff0000 in ?? ()
#20 0x0000000000010000 in ?? ()
#21 0x00000000ffd5ffd0 in ?? ()
#22 0x000b000800000000 in ?? ()
#23 0x0000000100000000 in ?? ()
#24 0x00000000ffffffff in ?? ()
#25 0x00180012ffff0000 in ?? ()
#26 0x0000000000010001 in ?? ()
#27 0x0000ffff002c0025 in ?? ()
#28 0x0027001c00000000 in ?? ()
#29 0x0001000000010000 in ?? ()
#30 0x0000000100420034 in ?? ()
#31 0x004f003e00010000 in ?? ()
#32 0x0000000000000000 in ?? ()
(gdb)
References
comment:7 by , 4 years ago
Another data point: I tried RC1 with similar results:
VirtualBox-6.1.0_RC1-134891-Linux_amd64.run
comment:8 by , 4 years ago
Hi,
In order to get some traction on this issue, would it be better if I switch to 6.1/RC1?
Thx!
comment:10 by , 4 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Replying to sunlover:
I could not reproduce the crash.
Replying to pablo_:
Due to no activity from Oracle, please close the ticket.
That was Oracle (sunlover) replying to you. Not sure if by "no activity" you meant "no immediate patch" for something that wasn't readily reproducible.
I'm going to go ahead and per your request close the ticket.
comment:11 by , 4 years ago
Follow the activity and you'll see there's no meaningful work being done by the vendor.
It is nonsense to try to characterize it as "no immediate patch"
Anyone can see that in an effort to make some/any progress, I provided a stack track.
It is important to understand that when people spend the time to gather data to report a bug, timely responses are warranted.
comment:12 by , 4 years ago
Furthermore, if you look at the timeline, you can see it took over two weeks for an initial response and so far 11 days and counting for a subsequent response.
When I reported issues before to Innotek, Frank and team were way more responsive.
comment:13 by , 4 years ago
Given socratis banned me on the forums, he decides to personally attack me as well on there:
And that's exactly why 'whyn0t' gets permanently banned for severe forum vandalism.
Their ego got hurt because they didn't hear back from an Oracle developer (which they did in the ticket). Same attitude in the ticket. I guess some people want immediate, personal attention, and if they don't get it they're holding their breath until they turn blue. And that's fine, as long as that affects only themselves. If their actions affect the community, there are going to be consequences..."
This is too bad.
I suppose for him, waiting for a month is immediate personal attention
The above is nonsense.
Furthermore, since when am I, the owner of my content, not allowed to delete it. I wrote it, I can remove it.
To set up a straw man to personally attack me is ridiculous.
comment:14 by , 4 years ago
This really looks to me like an unfortunate sequence of events. sunlover seems to have missed the fact that the symptom description showed that the VM process (on Linux host) is crashing. This means asking for a minidump was asking for the impossible, he should've asked for a core dump (which needs enabling, see https://www.virtualbox.org/wiki/Core_dump ).
Your debugging attempts were bound to not get far, because the VirtualBox packages don't contain debug infos (to reduce the download size), but the dev team could've worked from a core dump because we have debug info for all releases in our archive.
follow-up: 16 comment:15 by , 4 years ago
Hey Klaus,
Let's press on.
Wiki Tweak
The wiki needs an entry for openSUSE.
I am happy to make the change but if you rather handle it, here's the link for core dump:
https://www.suse.com/support/kb/doc/?id=3054866
core dump generated
I generated a core dump.
After I compressed it, it's 12 MiB. I could uuencode / split but it may contain sensitive information.
Is there an equivalent crash reporting tool that you'd like me to use for openSUSE? apport is a Ubuntu-ism.
Work-around Implemented
Per the sidebar conversation, I have my expectation set. I have a kludgy work-around.
follow-up: 17 comment:16 by , 4 years ago
Replying to pablo_:
Wiki Tweak
The wiki needs an entry for openSUSE.
I am happy to make the change but if you rather handle it, here's the link for core dump:
That wiki page has been updated with a #SUSE section and this link, thanks!
comment:17 by , 4 years ago
Replying to fbatschu:
That wiki page has been updated with a #SUSE section and this link, thanks!
Thank you for rolling the fix.
Let's sit tight for a bit as I try to create a sanitized VM that I can easily share its core dump.
I'll be back with an update. ;)
Thank you! -pablo
comment:18 by , 4 years ago
Good news. I created a simple test case.
I have uploaded the core and md5sum to my G Drive. Per the Core Dump Wiki, I sent the link to Alexander.
If needed, I can even upload the compressed .vdi.
Thx!
comment:19 by , 4 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=7&t=95478
You were supposed to follow these steps when you filed the bug, and provide a VBox.log: