Hello,
I am using a richeditcontrol and when debugging my program step by step, by openning the details of my richeditcontrol, my Visual Studio freeze during 10 seconds and then I am getting an timeout by the "OpenDocumentsBytes" property.
Visual Studio throws timeout exception for RichEditControl's properties during debugging
created 9 years ago
(modified 9 years ago)
Answers approved by DevExpress Support
created 9 years ago
(modified 9 years ago)
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
- v15.2.4Download Official Update
- v15.1.8Download Official Update
- v14.2.11Download Official Update
Show previous comments
(1)
You are welcome, Yannick!
Feel free to contact us if you have more questions regarding our products.
PS
7 years ago
Hello,
I am using DevExpress version 17.2.6 (Windows Forms) with Visual Studio 10 SP1 and get the same problems as described above. Hasn't this problem been fixed yet for Visual Studio 10?
Hi Patrick,
Please review the following ticket, which describes why this happens:
Snap - Debuging in Visual Studio - Function evaluation time out
Let me know if you have further questions.
Hi,
It is difficult to diagnose this problem based only on the provided information. Would you please send us a sample project that we can use to replicate this problem? This way, we will be able to research it and determine the cause of the problem. Your time and cooperation are greatly appreciated.
I look forward to your response.
Hello,
here is a sample. Set a breakpoint a the line "richEditControl1.Text = "Set Breakpoint here";" and then launch the Project.
When the programm reach the breakpoint, in your "Auto" variables, open the "richEditControl1" details and scroll down. At this moment my VS2013 freeze during 10 seconds and I am getting an timeout.
Hi,
We have successfully reproduced the behavior you described and passed this ticket to our developers for further research. It seems that when Visual Studio stops at the breakpoint, some of the RichEditControl properties aren't initialized yet, and when your try to check these properties, it takes too much time for Visual Studio to do that. As a workaround, I suggest you check the solution that I have found on the Internet: Function evaluation timed out when examining variables in debug/stepping through.
Please bear with us. We will notify you as soon as we make any progress.