So this is not the ideal way to correct the issue but here is my workaround:
open up the offending applications at a "safer" resolution--one much smaller than the maximum available. Start the offending applications, and you should observe no issues. Uping the resolution should then be possible without problems. I used 1024x768 as my safe resolution to get up to 1920x1080.
For multi-virtual monitor setups, you may also need to reorder the monitors in Display Preferences so that display 2 is on the left and display 1 is on the right--the opposite of default. At this point, upping both displays to the correct resolution was possible without the cycle spasms described in the original post.
Yep, it works now.
I unchecked "Always use the QML emulation layer provided by Qt Creator". After that, QtDesigner built a new and working qml2puppet layer. Thank you very much, again!
Greetings to Berlin,
Frime
The problem can be solved building GDB with a Python 2.7 or 3 in path. Python 2.6 from Centos 6.X lacks some feature which breaks the debugger integration for Qt Creator 3.1.2.
Python 2.6 could also break the debugger pretty printers for Qt Creator > 2.8.1 and < 3.2, but I haven't tested any other version than 2.8.1 and 3.1.2.
More info in can be found in QTCREATORBUG-13462.