Custom Query (16363 matches)
Results (2023 - 2025 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. |
|||
| #13186 | duplicate | Changing VM Group causes the .vbox snapshot statefile value to become corrupt, making snapshots invalid | ||
| Description |
Changing VM Group causes the .vbox snapshot statefile value to become corrupt, making snapshots invalid Basically, I have some VMs that have several sequential snapshots taken. And sometimes I move those VMs into a group, and sometimes I move them out of a group. It turns out that this causes damage to the .vbox file, specifically the snapshot statefile value. This is on a Windows 8.1 x64 host. Inside of the .vbox file, I see lines like: <Snapshot uuid="{496ab03a-2741-44ff-8eb9-f65ef4903835}" name="Snapshot 1" timeStamp="2014-07-14T19:27:23Z" stateFile="Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-14T19-27-23-544711400Z.sav"> .... <Snapshot uuid="{fab398f5-5b9f-47f4-a1ae-360584481820}" name="Snapshot 2" timeStamp="2014-07-14T21:39:20Z" stateFile="Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-14T21-39-20-146504400Z.sav"> .... <Snapshot uuid="{d1a3af0f-7f1b-4628-acc0-737f535dfa3b}" name="Snapshot 3" timeStamp="2014-07-15T04:19:57Z" stateFile="Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T04-19-57-096021800Z.sav"> .... <Snapshot uuid="{9455a652-f640-4769-bff8-06812d39549c}" name="Snapshot 4" timeStamp="2014-07-15T21:57:44Z" stateFile="Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-58-06-472936600Z.sav/Snapshots/2014-07-15T21-57-44-771739300Z.sav"> Every time I move the VM out of a group, and back into a group, the "chain" of ".sav" files for that value keeps growing. This later causes problems, I believe, when snapshots are either copied in a cloning process, or attempted to be deleted. Can you please confirm that this "stateFile" value is being corrupted? Thanks, Jacob |
|||
| #10849 | obsolete | Changing VM names breaks snapshot path, Causes ProgressProxy error | ||
| Description |
<HardDisk uuid="{xxx}" location="C:/Users/Era/VirtualBox VMs/Base/DirectVM.vdi" format="VDI" type="Normal">
</HardDisk>
|
|||

