Doesn't happen on my computer.

No issues on my system either. OS X 10.9.4, Mathematica 10.0.

I am using OSX and cannot reproduce the problem. It appears that there is dynamic content which runs into problems.

It appears that several "dynamic" items that are started automatically. This is a wild guess but you might want to try to get rid of as many as possible. You might for example want to temporarily disable the suggestions bar and the autocompletion:

http://support.wolfram.com/kb/11466

You can also disable the dynamic highlighting in that same preferences menu. You might also want to change the dynamic updating and DynamicEvaluationTimeout in the option inspector. The more of the "intrinsic" dynamical content you switch off for this test the better. Perhaps that helps to narrow down what the problem is.

Cheers,

Marco

I've tried everything suggested. Unfortunately, the problem persists.

I even went through the process of reinstalling a fresh Win 8.1 and then MMA V10 (nothing else), but the problem persists. The only difference being the "Disable Dynamic Evaluation" dialog does not pop up anymore.

I did find out that the frontend does not lock up indefinitely. It will eventually come back (haven't timed it... it is many, many minutes). As soon as I interact with the plot, it locks up again. As you suggested, Sean, it is the interaction with the plot that is locking up the frontend.

At this point, I am disappointed in the lack of response I've received from support@wolfram.com. I've contacted them 3 times now. I included the notebook, SystemInformation[], and DxDiag output files. I've only received an initial computer generated response. I appreciate the response from those that posted here on the Wolfram Community. However, it seems that Wolfram support is unconcerned. This is the 1st time in years that I've felt my Premier Service subscription is not a good value. My issue may be isolated, but it is real and it is somewhat similar to other issues I've seen posted here (eg, the "slow startup times...") and Stackexchange.

To reiterate what I mentioned in posts above:

1. The issue does NOT occur when running in Win 8.1 Safe Mode.
2. The issue does NOT occur in version 9 (on the exact same PC).
3. The issue still occurs after a clean install of Win 8.1 and clean install of v10.0.

I think those 3 pieces of information, taken together, point to a change in v10.0.

David,

Do you also happen to have a wireless mouse and keyboard, like others who have reported slowness in startup? (I like to eliminate this as a possibilty; I am not able to reproduce your issue (also running Windows 8.1)).

Thanks to all that responded. I have a positive outcome to report.

Later this afternoon, I received a response from support. I happen to have multiple input devices (all USB) attached to my PC. The developers suggested that I remove all input devices except for a generic mouse and keyboard. After restarting with just those 2 devices, Plot3D/Graphics3D worked as expected... no frontend lockups.

Following that test, I began to shut down and reconnect my input devices one by one, testing Plot3D/Graphics3D after connecting each device. Plot3D/Graphics3D worked as expected after each step. So, now I have all my original devices connected and version 10.0 frontend is running Plot3D/Graphics3D flawlessly.

I'm not sure what the underlying problem was, but I suspect that it has to do with how version 10.0 interfaces with some USB input devices and how some devices maintain/present their state (even through a restart). Something certainly must have changed from version 9 to version 10. I'm guessing that removing/reconnecting the devices was adequate to put the devices into a state that version 10.0 expected to handle. Unfortunately, I don't have any way of knowing which devices may have caused version 10.0 to have an issue since there was no longer an issue as I reconnect my devices. Unless a specific device can be isolated as being troublesome, the recommendation would be to remove all input devices and then reconnect.

I don't understand why reinstalling Win 8.1 didn't correct the issue. I don't recall if I shut down the PC during this process.

I can provide a list of the input devices on my PC:

• Steelseries MERC Programmable keyboard
• Razer Hex Naga Programmable mouse
• Wacom Intuos 3 Pen Tablet
• 3DConnexion Spacenavigator
• Logitech Extreme 3D Pro Joystick

Thanks to WRI support for responding and suggesting this procedure. It did occur to me to consider disconnecting devices. I had disconnected the Pen Tablet and Spacenavigator prior to hearing from support. However, that had no effect so I didn't even think of disconnecting my mouse/keyboard/joystick.

Hopefully, this information will be helpful in resolving the problem for future releases and/or for other users.

David,

We received this hardware today and are able to reproduce the lockup you describe and are investigating the issue. There is no workaround at this point (other than disconnecting this hardware).