Then, I checked "Collect trace" and clicked on "Attach". Then in the Profiler's main window, I checked the "attached to application" option and highlighted the running virtualbox line. I went in the OpenGL Profiler's preferences, gave a name to the "Remote Profiling Name" and set a password for it, and checked the "Enable remote profiling" box. I am not sure what I am doing wrong, but I am unable to see any traces and the frame rate always shows as "0.0 FPS" in the profiler main window, which I am guessing is wrong. Please, reproduce "windows motion lag" and attach or share verbose traces. Just try to connect to OpenGL Profiler 'remotely': I'll try to compare duration of OpenGL API calls with my case when NO drawing lag happens Detach Profiler, export verbose trace data to a txt file, compress and share it.Replay the drawing lag by moving a window inside VM during ~10 seconds.I am guessing that opcenter witnessed the crash on a 5.1.* version. Note that I am currently running 5.0.34 and I was going to collect traces for both 5.0.34 and then to 5.1.* after installing it (again). My VirtualBox (running RedHat) also dies as soon as I click on "attach" in OpenGL Profiler. Enable "Collect traces" in OpenGL Profiler and attach it to VirtualBox process.Close all other VirtualBox clients including VirtualBoxManager.Choose a VM with enabled "3D acceleration" and GA installed, start that VM.Download OpenGL Profiler from (AppleID is required).Mac is a late 2013 retina with hybrid intel/nvidia graphics.Ĭould someone collect OpenGL Profiler data in this way: With debian and lxde, installing guest additions sometimes temporarily solves the issue, but then it spontaneously comes back. you can even run the mouse in loops or circles than sit back and watch the window follow its trail. open an app window and try to drag it around. To see the bug, just run a live installer like fedora, debian, or red hat. Windows and linux hosts are not affected. all other desktops or window managers ive tried also show this bug, lxde, xfce, fvwm, and kde ![]() gnome-desktop, in ubuntu, debian, or red-hat, still has the bug. The only exception is ubuntu desktop, and only when guest extensions are installed. Maximized apps (full screen) are not affected by this bug and will resize with the virtualbox window in both directions as fast as can be expected. ![]() horizontal is sometimes almost at normal speed. drag and resize both seem a little faster horizontally and vertically. then it takes several seconds for the windows to move or resize following the drag event. When using os x (10.12.2) as the host and linux guests, gui performance is ok, except for dragging or resizing windows within the gui. Developer update: this problem needs user investigation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |