Custom Query (16363 matches)
Results (2185 - 2187 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15871 | fixed | Changeset 63628 - possible destroy of locked critical section? | ||
| Description |
In https://www.virtualbox.org/changeset/63628/vbox there is a change that moves RTCritSectLeave before audioMixerStreamDestroyInternal, but on the other hand the RTCritSectLeave will not be called when previous assignment to rc2 on line 1627 (rc2 = audioMixerSingRemoveStreamInternal...) fails. This looks like a bug - the unlock (RTCritSectLeave) should be called always if lock (RTCritSectEnter) succeeds. |
|||
| #15869 | duplicate | VBoxNetNat.exe: The instruction at 0x referenced memory at 0x. The memory could nom be written. | ||
| Description |
I often (unpredictably) get this error that kills my VM's networking until I restart or save/restore: The instruction at 0x referenced memory at 0x. The memory could nom be written. VBoxNetNat.exe I can't find a deliberate trigger, though it may possibly be related to network throughput. Or talking to a Kubernetes cluster. |
|||
| #15868 | worksforme | "double free or corruption" error when installing guest additions | ||
| Description |
Windows 7 host (on Lenovo x250 Laptop) Debian guest The issue started with 5.0 or 5.1 (not quite sure, things seem to work), and happened on several VMs (all Debian) with several updates (5.1.2, 5.1.4) /media/cdrom$ sudo sh VBoxLinuxAdditions.run Verifying archive integrity... All good. Uncompressing VirtualBox 5.1.4 Guest Additions for Linux........... VirtualBox Guest Additions installer Removing installed version 5.1.2 of VirtualBox Guest Additions... vboxadd.sh: Stopping VirtualBox Additions. update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64 update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 vboxadd-service.sh: Stopping VirtualBox Guest Addition service. *** Error in `systemctl': double free or corruption (fasttop): 0x00007f233d4bd2a0 *** Copying additional installer modules ... Installing additional modules ... vboxadd.sh: Building Guest Additions kernel modules. vboxadd.sh: You should restart your guest to make sure the new modules are actually used. vboxadd.sh: Starting the VirtualBox Guest Additions. You may need to restart the the Window System (or just restart the guest system) to enable the Guest Additions. /media/cdrom$ uname -a Linux dweb642 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux Googling "double free or corruption" seems to show it might be a systemd issue... /media/cdrom/$ cat /var/log/VBoxGuestAdditions.log vboxadd.sh: failed: Cannot unload module vboxguest. |
|||

