.NET Winforms Waitmessage() is misleading in purepaths

Question

Question by Mark G. · May 07, 2013 at 01:53 PM ·

.NET Winforms Waitmessage() is misleading in purepaths

I have a .NET rich client application (both winforms and WPF), which shows a lot of winforms waitmessage() calls in the purepaths, some of these last 20 seconds or longer. I would think that waitmessage() should end the purepath, since the thread is suspended. Is anyone else seeing this behavior?

0

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 1 · 2013-05-07T14:39:26Z

Answer by Andreas G. · May 07, 2013 at 02:39 PM

Hi Mark

You are right. These methods unfortunately show up as main hotspots even though all they really do is wait for e.g: another thread to complete or - as it is in your case - the user input

Andi

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 2 · 2013-05-07T14:31:01Z

Answer by Mark G. · May 07, 2013 at 02:31 PM

After further investigation, I think this may be more an issue with modal dialogs, these waitmessage() calls are inside rundialog() calls.

0 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

.NET Winforms Waitmessage() is misleading in purepaths

2 Replies

Join the conversation!

NAM 2019 SP3 is available

LIVE WEBINAR

Follow this Question

Forum Tags