Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Qt applications will crash if I change the clipboard on Windows
-
On Windows, if I change the clipboard in any application, Qt applications will crash, and its CPU usage will be higher.
If it crashes, it will be busy for unknown reason, and the OS won't tell me something wrong like accessing protected memory.
I'm using Qt 4.7.4, and Windows XP with SP3.
Debug info:
7C92E4ED lea ecx,[ecx]
7C92E4F0 mov edx,esp
7C92E4F2 sysenter
7C92E4F4 ret <- ECX: 0114E034 EDX: 7C92E4F4 ESP:0114E034
7C92E4F5 lea esp,[esp]
-
I had another kind of this problem before with Qt Creator. I had a delay when copying something like text on another application. But i don't have same problem with 2.3.1.
-
Your actual C++ code that copies to the clipboard would be helpful.
-
[quote author="Volker" date="1323609180"]Your actual C++ code that copies to the clipboard would be helpful.[/quote]
It's not about coding on Qt Creator. Assume you have Qt Creator opened and other side you have a notepad on windows. Then you write some text on notepad and select your text and Ctrl + C. Now bring your Qt Creator. You'll see it's busy for unknown reason!
-
Using Editor and Wordpad on a Vista box and copying some text to Creator 2.4 RC, I cannot reproduce the error.
-
[quote author="mohsen" date="1323609679"][quote author="Volker" date="1323609180"]Your actual C++ code that copies to the clipboard would be helpful.[/quote]
It's not about coding on Qt Creator. Assume you have Qt Creator opened and other side you have a notepad on windows. Then you write some text on notepad and select your text and Ctrl + C. Now bring your Qt Creator. You'll see it's busy for unknown reason![/quote]
Thank for your better description.
Mohsen's problem looks the same as mine. Each Qt app (like Qt Creator) on Windows(Language: Chinese) has this problem. And it won't crash on Linux.
-
Ah, that would explain the non-error on my latin1 box. In that case, I recommend opening an issue on the "public bugtracker":https://bugreports.qt.nokia.com. Don't forget to search if an issues has already been openend for the same problem.
