[ros-diffs] [reactos] 01/01: [WIN32SS] CORE-16738 Comment an assert

[Joachim Henze]

https://git.reactos.org/?p=reactos.git;a=commitdiff;h=87f6c82d854583f715468…

commit 87f6c82d854583f71546841f4432f57e4a2d6c99
Author:     Joachim Henze <Joachim.Henze(a)reactos.org>
AuthorDate: Tue Apr 21 23:26:47 2020 +0200
Commit:     Joachim Henze <Joachim.Henze(a)reactos.org>
CommitDate: Tue Apr 21 23:26:47 2020 +0200

    [WIN32SS] CORE-16738 Comment an assert
    
    It popped up 2-3 times for me during several
    months of ros usage and I could continue without
    noticing any side effects.
    Giannis who once added it, was ok with commenting it.
    
    His words:
    This assertion isn't something fatal,
    the worst thing that can happen from continuing on it would be
    to make the thread get awake more times than it should.
---
 win32ss/user/ntuser/misc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/win32ss/user/ntuser/misc.c b/win32ss/user/ntuser/misc.c
index 99066d90fda..72706fa7f84 100644
--- a/win32ss/user/ntuser/misc.c
+++ b/win32ss/user/ntuser/misc.c
@@ -724,8 +724,8 @@ void UserDbgAssertThreadInfo(BOOL showCaller)
     ASSERT(pci->ulClientDelta == DesktopHeapGetUserDelta());
     if (pti->pcti && pci->pDeskInfo)
         ASSERT(pci->pClientThreadInfo == (PVOID)((ULONG_PTR)pti->pcti -
pci->ulClientDelta));
-    if (pti->pcti && IsListEmpty(&pti->SentMessagesListHead))
-        ASSERT((pti->pcti->fsChangeBits & QS_SENDMESSAGE) == 0);
+    //if (pti->pcti && IsListEmpty(&pti->SentMessagesListHead))
+    //    ASSERT((pti->pcti->fsChangeBits & QS_SENDMESSAGE) == 0);
     if (pti->KeyboardLayout)
         ASSERT(pci->hKL == pti->KeyboardLayout->hkl);
     if(pti->rpdesk != NULL)