1

Topic: The first message comes late

Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. Can at somebody there is an explanation of this situation?

2

Re: The first message comes late

Hello, _NN _, you wrote: _NN> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. _NN> can at somebody there is an explanation of this situation? Only the assumption - something can lock  a flow? Any initialization, reversal to file system, network shares?

3

Re: The first message comes late

Hello, V. Zudin, you wrote: SVZ> Hello, _NN _, you wrote: _NN>> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. _NN>> can at somebody there is an explanation of this situation? SVZ> only the assumption - something can lock  a flow? Any initialization, reversal to file system, network shares? All in a separate flow. There is a flow, in it create a window and we wait. WM_GETMINMAXINFO comes sometimes with lateness about 6 seconds.

4

Re: The first message comes late

_NN> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. _NN> can at somebody there is an explanation of this situation? At Mr. Debaggera the explanation precisely is.

5

Re: The first message comes late

Hello, ononim, you wrote: _NN>> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. _NN>> can at somebody there is an explanation of this situation? O> at Mr. Debaggera the explanation precisely is. To Debug a kernel it is offered?

6

Re: The first message comes late

_NN> Hello, ononim, you wrote: _NN>>> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. _NN>>> can at somebody there is an explanation of this situation? O>> at Mr. Debaggera the explanation precisely is. _NN> to Debug a kernel it is offered? To begin with to look at all  stacks for a moment

7

Re: The first message comes late

Hello, ononim, you wrote: _NN>> to Debug a kernel it is offered? O> to begin with to look at all  stacks for a moment  There anything especial it is not visible.

8

Re: The first message comes late

Hello, _NN _, you wrote: _NN> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. 1. How quickly comes WM_CREATE? 2. Note down all structures MSG after GetMessage

9

Re: The first message comes late

_NN>>> to Debug a kernel it is offered? O>> to begin with to look at all  stacks for a moment  _NN> There anything especial it is not visible. Well it is direct . It is possible an output windbg after sequence of commands:.symfix.reload ~ *kv ffff? Well and if to be engaged in a guessing on a coffee thick - it is possible to assume that is  a window (it is absolutely optionally specific here here and even it is optional that you) which long does not process a message. Or what procedure that   - but it would be already visible on a stack.

10

Re: The first message comes late

Hello, Pavel Dvorkin, you wrote: PD> Hello, _NN _, you wrote: _NN>> Sometimes there is a situation when between creation of a window and the first message transits more than 5 seconds. PD> 1. How quickly comes WM_CREATE? Sometimes for milliseconds, sometimes about 6 seconds a beret. PD> 2. Note down all structures MSG after GetMessage

11

Re: The first message comes late

Hello, _NN _, you wrote: _NN> to Debug a kernel it is offered? Generally, I never faced the such, or did not note. Except window creation any actions with it become? As debugging and problem division in halves I can advise SetWinEventHook, events of creation of a window (event_object_create) still there arrive before messages depart.

12

Re: The first message comes late

Hello, _NN _, you wrote: PD>> 1. How quickly comes WM_CREATE? _NN> Sometimes for milliseconds, sometimes about 6 seconds a beret. Whether there is a difference in start under a debugger and without it?

13

Re: The first message comes late

Hello, Pavel Dvorkin, you wrote: PD> Hello, _NN _, you wrote: PD>>> 1. How quickly comes WM_CREATE? _NN>> Sometimes for milliseconds, sometimes about 6 seconds a beret. Whether PD> there is a difference in start under a debugger and without it? A problem that it happens irregularly and not on my computer. It is possible to try to compare to a debugger.

14

Re: The first message comes late

Hello, _NN _, you wrote: _NN> the Problem that it happens irregularly and not on my computer. At me suspicion that there any . Is here such https://shiftlock.wordpress.com/2011/06 … -detector/ Alas, works or not, I can not judge - at me Windows 10, and the driver unsigned, it would not be desirable to potter.