Custom Query (16363 matches)
Results (2323 - 2325 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17664 | fixed | Crash in hdaR3Timer, Fedora 27 host, Oracle Linux 7.2 guest -> fixed in 5.2.22 | ||
| Description |
VirtualBox crashes when any gnome based application is started, including gdm and gnome desktop, but only with guest additions installed (3d acceleration disabled). With 3d acceleration enabled I get kernel panics and oopses, system can not load. Worked fine in 5.2.6. Guest kernel is 3.8.13-98.7.1.el7uek.x86_64 Host system - Fedora 27 x86_64 |
|||
| #3217 | fixed | Crash in icmp_find_original_mbuf => Fixed in 3.1.4 | ||
| Description |
VirtualBox crashed - I was trying to ping another host at the time, although the guest was unresponsive, and then crashed. (Also, I had just plugged my USB keyboard and mouse back in, if that's relevant somehow.) Fragment from the Apple crash report (attached): Thread 13 Crashed: 0 VBoxDD.dylib 0x1c7bcf73 icmp_find_original_mbuf + 659 1 VBoxDD.dylib 0x1c7bf301 sorecvfrom + 497 2 VBoxDD.dylib 0x1c7bc0f1 slirp_select_poll + 1393 3 VBoxDD.dylib 0x1c7b0dd1 drvNATAsyncIoThread(PDMDRVINS*, PDMTHREAD*) + 449 4 VBoxVMM.dylib 0x014b5285 pdmR3ThreadMain(RTTHREADINT*, void*) + 213 5 VBoxRT.dylib 0x01361b60 rtThreadMain + 64 (thread.cpp:641) 6 VBoxRT.dylib 0x0138b814 rtThreadNativeMain(void*) + 132 (thread-posix.cpp:193) 7 libSystem.B.dylib 0x91dc0095 _pthread_start + 321 8 libSystem.B.dylib 0x91dbff52 thread_start + 34 I am using 2.1.0 instead of 2.1.2 because of a frequently-occurring crash bug in 2.1.2. I guess I'll try to avoid pinging from the guest, to avoid this bug! |
|||
| #5564 | duplicate | Crash in seemless mode while doing a software compile | ||
| Description |
I've listed 'Component' as other as I'm not sure which specific component is involved. I'm running 3.0.12 (AMD64 build) on Mandriva 2009.1 64bit, running a 32bit Windows XP guest. I recently needed to kick off a compile of my company's software (haven't had to for some time), and find that about 2/3rds of the way through VirtualBox crashed - the log showed a GURU_MEDITATION message. At this time I was running 3.0.8. I restarted, tried again, and got a crash again, though in a different spot. I decided then to upgrade this morning to 3.0.12 just in case there was something there related (changelog didn't show anything obvious) - but trying the build again resulted in another crash. In all the above tests my guest was running in seamless mode. For some strange reason I decided to switch out of seamless mode and try it. So after a restart of the guest (seamless doesn't go in and out smoothly on my system - but that's another issue) I kicked of the build again. Now it's working - the build completes without crashing. So I don't know why seamless would make a difference - or if something else in the environment has magically changed and seamless is a red herring. I've attached: VBox-crash-3.0.8.log - which is the log from the first crash in 3.0.8 VBox-crash-3.0.12.log - which is the log from the crash in my first attempt in 3.0.12 |
|||

