Changes between Initial Version and Version 1 of Ticket #16436, comment 95
- Timestamp:
- Oct 3, 2018 10:11:03 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16436, comment 95
initial v1 3 3 I believe a number of users affected by this bug didn't read this ticket just because the title sounds quite different to the problem they see (in fact, I was going to skip it in the search engine, but no other tickets matched the problem, so I decided to read it supposing it was unrelated, and to my surprise, this is exactly the bug I was getting). 4 4 5 I'm experiencing this bug with a brand new 2018 MacBook Pro (15 '', 6-core i9, 32GB RAM), and it's pretty annoying. I noticed it because I was using Revit 2019 on a Windows 7 x64 VM (my host is High Sierra 10.13.6), and while dragging a 3D view, a few frames were rendered, and then the VM became like frozen: no mouse pointer, no screen updates, nothing. Reading this ticket, I found the direct USB mouse trick, and it works (in fact, if I drag a Revit 3D view with the Trackpad and it becomes stuck, I can make it resume by dragging the (direct USB) mouse.5 I'm experiencing this bug with a brand new 2018 MacBook Pro (15inch, 6-core i9, 32GB RAM), and it's pretty annoying. I noticed it because I was using Revit 2019 on a Windows 7 x64 VM (my host is High Sierra 10.13.6), and while dragging a 3D view, a few frames were rendered, and then the VM became like frozen: no mouse pointer, no screen updates, nothing. Reading this ticket, I found the direct USB mouse trick, and it works (in fact, if I drag a Revit 3D view with the Trackpad and it becomes stuck, I can make it resume by dragging the (direct USB) mouse. 6 6 7 7 My first guess is that the cause was related because either this i9 was too new and proper virtualization for it wasn't implemented in VirtualBox yet, and it was being used in a way that all its performance was invested in Mesa/Gallium OpenGL and no cycles were left for updating the UI. Another guess was that it could perhaps be related to memory access (the VM getting temporarily stuck because of some memory access bug)... I had a quick feeling that it could be a matter of mouse input, but I didn't take it too seriously. I mention my first guesses just to show that other Mac users suffering this bug can be searching for it following totally wrong clues.
