VirtaulBox 4.3 - windows jump like crazy

[VBoxFan2000]

Hi.

Just updated to VBox 4.3.0 and noticed its pretty much unusable because the VBox window (on the Host) is jumping between my screens like crazy

Try this: Move VBox window to second screen, click "maximize" button on the window bar. Result: Window jumps back to first screen for no apparent reason and appears restored again

I'm back to 4.2.x for now. Hope this will get fixed...

[VBoxFan2000]

Really, nobody else noticed this?

I also noticed that VBox window, while maximized, suddenly jumps back to "restored" state for no apparent reason during boot up.

Either 4.3 is really seriously broken or I miss something...

(BTW: Host is Windows 7 x64, guests i tried Debian 7 and Mint 15, but problem does not seem to depend on the guest)

[noteirak]

Minimum information needed for assistance.

[VBoxFan2000]

As you want:

The version of VirtualBox you are using, and whether you have installed the Guest Additions (in the guest).
4.3.0, yes

Host & Guest make and version including 32 or 64 bit, and the amount of memory available to both.
Host: Windows 7 (64-Bit) with SP-1, Guest: Debian Linux 7 as well as Mint Linux 15, Memory: 4GB (Host) and 1536 MB (Guest)

Guest log file (as an attachment)
See below.

[VBoxFan2000]

I made a short screen recording that shows the issue.

(please find the download instructions attached to my post, as the board doesn't allow me to post them directly)

[Ramshankar]

I had passed on this to our GUI expert and he mentioned it was reproducible, so a fix will eventually be available. Can't mention any ETA for the fix though.

[VBoxFan2000]

Glad you can confirm it. How could such problem be overlooked in a new major release?

[Ramshankar]

Glad you can confirm it. How could such problem be overlooked in a new major release?

Probably because nobody tested & reported the bug in the beta period on multiple monitors on a Windows 7 host while using the GUI and using full-screen mode? While we have an extensive (and ever growing) automated test suite, there is still (and probably always will be) many cases that escapes our testing. Not to sound defensive or justifying the lapse in our testing, but the VirtualBox code runs on far more hosts and guest combinations than any other hypervisor.

Thank you for the bug report

[bulletmark]

I run VirtualBox 4.3.0 on both my Linux Ubuntu 13.04 host and my Mac OSX 10.8.5 host and note that this problem happens on both those platforms also. So it is a universal bug.

[Dsen]

How could such problem be overlooked in a new major release?

We have no quality testing team except you our dear users, so since that bug was noticed only *after* 4.3.0 release, it (I hope) can be fixed to 4.3.2 only.

[VBoxFan2000]

Yeah, but this was a quite obvious annoyance that everybody should have noticed who at least tried using the software in some way. Not some exotic bug triggered under rare circumstances

Anyway, I realized that it was indeed fixed in v4.3.2. So thanks!

[Perryg]

Yeah, but this was a quite obvious annoyance that everybody should have noticed who at least tried using the software in some way. Not some exotic bug triggered under rare circumstances
Anyway, I realized that it was indeed fixed in v4.3.2. So thanks!

I think you are missing the point. The users that did participate in the beta testing did not have this issue, which is not out of the ordinary since it would more than likely be triggered by a difference in host hardware or OS. Maybe you will participate in the next one and life will be good for you again.