Timeline for Visual Studio debug break points freezing app
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2013 at 12:11 | history | edited | FeliceM | CC BY-SA 3.0 |
added 122 characters in body
|
| Jun 17, 2013 at 11:09 | comment | added | FeliceM | @HansPassant, I accept what you say but is a fact that with or without break points I have a difference and I do not understand why. With the same stream of data in the first case the app freezes in the second case, without break points, it is working fine. | |
| Jun 17, 2013 at 10:58 | history | edited | FeliceM | CC BY-SA 3.0 |
Added some clarification
|
| Jun 17, 2013 at 10:56 | comment | added | Hans Passant | Breakpoints induce no overhead at all unless you made them conditional. | |
| Jun 17, 2013 at 10:53 | comment | added | FeliceM | @HansPassant, thanks Hans. I tought the same but the problem is occurring only if I have break points active as explained in my post. Without the break points the snipet is working fine with the full stream of data. I am looking at the relation betwwen the break point and the problem. To find a solution I need to understand how the breake points interact with the process. | |
| Jun 17, 2013 at 10:28 | comment | added | Hans Passant | The posted code is very unlikely to be related to the problem. The typical issue is using the DataReceived event and calling Begin/Invoke too often. Pummeling the UI thread with invoke requests and making it go catatonic when it can't keep up and stops painting and responding to user input. Which you fix by making the DataReceived event doing more work, collecting the entire device response before invoking. Ignoring the SerialPort.Read() return value is also a classic mistake. None of this is visible in the snippet. | |
| Jun 17, 2013 at 9:55 | answer | added | WiiMaxx | timeline score: 1 | |
| Jun 17, 2013 at 9:55 | comment | added | Uwe Keim |
Trace.TraceInformation?
|
|
| Jun 17, 2013 at 9:52 | comment | added | WiiMaxx | you could also write to your output window in VS but i don't know how to do it i just now you can do it :D | |
| Jun 17, 2013 at 9:50 | comment | added | FeliceM | Thanks for the advice. It is for sure a great alternative but does not give a real time vision of what is happening. However, I did not considered it before and I will try it. | |
| Jun 17, 2013 at 9:48 | history | edited | FeliceM | CC BY-SA 3.0 |
deleted 8 characters in body
|
| Jun 17, 2013 at 9:47 | comment | added | WiiMaxx | you could create an Logfile as alternative to breakpoints | |
| Jun 17, 2013 at 9:35 | history | edited | FeliceM | CC BY-SA 3.0 |
edited body
|
| Jun 17, 2013 at 8:55 | history | edited | Damien_The_Unbeliever |
edited tags
|
|
| Jun 17, 2013 at 8:54 | history | edited | Satpal | CC BY-SA 3.0 |
brake changed to break
|
| S Jun 17, 2013 at 8:54 | history | suggested | Satpal | CC BY-SA 3.0 |
brake changed to break
|
| Jun 17, 2013 at 8:53 | review | Suggested edits | |||
| S Jun 17, 2013 at 8:54 | |||||
| Jun 17, 2013 at 8:50 | history | edited | FeliceM | CC BY-SA 3.0 |
added 73 characters in body
|
| Jun 17, 2013 at 8:40 | history | asked | FeliceM | CC BY-SA 3.0 |