OK, I think there’s a few issues here. First, it looks like you’re actually running within a virtual machine? In which case I’m impressed you got MRView to work at all. I’m actually surprised to see the GL version reported to be 3.3, I wouldn’t expect virtual machines to be able to support hardware acceleration at this stage. Maybe VMware has made progress on this of late, or more likely, it’s using software rendering, which will be really slow - too slow to be useable for anything but the simplest tasks.
The other issue is that the drivers you are using probably aren’t quite up to it. It’s reporting using the open-source mesa drivers, version 10.3.2 - in my experience, you need at least mesa 10.6 for things to work properly with OpenGL 3.3.
The thing is, MRView uses modern OpenGL to handle the rendering - this is what allows us to render what are really very complex scenes with interactive frame rates. While virtual machines are handy, they generally prevent direct access to the hardware, making MRView (or any other intensive OpenGL application) essentially unusable. I’d strongly recommend you try running it natively if you can…