Custom Query (16363 matches)
Results (1780 - 1782 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3164 | fixed | Regression: main window position shift on each VB startup | ||
| Description |
Whenever I run VB 2.1.2, the main control window is shifted down by 70 pixels. Suppose the coordinates were (x_pos, y_pos, x_len, y_len) when VB was closed. The next time VB is run, the window will be at (x_pos, y_pos+70, x_len, y_len). As a test, I performed 10 subsequent start-quit cycles without manually moving the window around. It ended up being mostly sunk below the bottom, so I had to stop the test to avoid it going totally off-screen and thereby becoming inaccessible. In the first run after I upgraded from 2.0.6 to 2.1.2, I observed a glitch that might be related: VB's main window was positioned at (0,0) rather than (0,44), with its handle being hidden behind the menu bar. Due to the missing handle, this looked as if the GUI switched to full-screen. I got it back to normal by hiding and then un-hiding VB. |
|||
| #3168 | fixed | BAD_POOL_CALLER Upon Booting Windows Vista => fixed in SVN | ||
| Description |
Virtualbox crashed my computer today when I resumed the computer from hibernation. Here's the !analyze -v output from WinDbg: 1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this
is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000110b, (reserved)
Arg3: 080d0003, Memory contents of the pool block
Arg4: 872fb4f8, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: 872fb4f8 Nonpaged pool
FREED_POOL_TAG: VBNF
BUGCHECK_STR: 0xc2_7_VBNF
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 824fc00c to 824db0e3
STACK_TEXT:
88d63754 824fc00c 000000c2 00000007 0000110b nt!KeBugCheckEx+0x1e
88d637cc 82a81370 872fb4f8 00000000 88d637f8 nt!ExFreePoolWithTag+0x17f
88d637dc 8c2a8b6d 872fb4f8 00000000 00000000 ndis!NdisFreeMemory+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
88d637f8 8c2a8ff8 84e4915c 84e49368 84e49100 VBoxNetFlt+0x2b6d
88d63818 8c2a9447 8c2b5630 00000000 84e49100 VBoxNetFlt+0x2ff8
88d6383c 8c2a720d 84e49100 88d6396c 88d63898 VBoxNetFlt+0x3447
88d6385c 8c2a7349 8c2b5630 88d63898 88d63888 VBoxNetFlt+0x120d
88d63880 8c2a9d04 8c2b5630 88d63898 88d63990 VBoxNetFlt+0x1349
88d63980 8c2aa2ad 88d639a0 869f7b88 00000000 VBoxNetFlt+0x3d04
88d639a8 82b504b1 88d63a44 88d639d0 8627a454 VBoxNetFlt+0x42ad
88d63a3c 82b50129 00000000 84243f00 82ab0918 ndis!ndisInitializeBinding+0x23b
88d63ac8 82b5ef67 8630a0e8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88d63aec 82b5f1e1 00000000 8592b560 00000000 ndis!ndisIMInitializeDeviceInstance+0x93
88d63b0c 8c0e1329 861c0b98 873e75d8 8592b560 ndis!NdisIMInitializeDeviceInstanceEx+0x100
88d63b58 82b504b1 88d63bf4 88d63b80 8613c68c dne2000+0xa329
88d63bec 82b50129 00000000 853da030 00000000 ndis!ndisInitializeBinding+0x23b
88d63c78 82b65e89 8623c0e8 00000000 00000000 ndis!ndisCheckAdapterBindings+0x170
88d63d34 82b4e013 848e59c8 8623c0e8 88d63d7c ndis!ndisDevicePowerOn+0x515
88d63d44 82446445 848e59c8 00000000 8427fd78 ndis!ndisWorkItemHandler+0xe
88d63d7c 825e3b18 848e59c8 536a4906 00000000 nt!ExpWorkerThread+0xfd
88d63dc0 8243ca2e 82446348 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+2b6d
8c2a8b6d 8b8694010000 mov eax,dword ptr [esi+194h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: VBoxNetFlt+2b6d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 497765d0
FAILURE_BUCKET_ID: 0xc2_7_VBNF_VBoxNetFlt+2b6d
BUCKET_ID: 0xc2_7_VBNF_VBoxNetFlt+2b6d
Followup: MachineOwner
---------
1: kd> lmvm VBoxNetFlt
start end module name
8c2a6000 8c2b9b00 VBoxNetFlt (export symbols) VBoxNetFlt.sys
Loaded symbol image file: VBoxNetFlt.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
Image name: VBoxNetFlt.sys
Timestamp: Wed Jan 21 10:13:36 2009 (497765D0)
CheckSum: 000164D2
ImageSize: 00013B00
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
|
|||
| #3169 | fixed | Guru mediation (pgmPoolTrackPhysExtDerefGCPhys) while linux guest shutdown/log out | ||
| Description |
After upgrade VBox from 2.1.0 to 2.1.2 (on WinXP SP2) guest OS (AltLinux Desktop 4.1) crashes with the message "A critical error has occured while running the virtual machine...". It happens on guest shutdown/user logout. The Guest Additions was upgraded from 2.0.6 to 2.1.2 (because 2.1.0 did not work properly with keymap switching). Downgrading the Guest Additions to 2.0.6 did not solve the problem. |
|||

