search

DiscordMessenger / dm

Discord Messenger is a free Discord-compatible messaging client targeting both new and old Windows.
MIT License
874 stars 18 forks source link

[Bug] ReactOS cannot properly run dm upon attempting to login #20

Closed Midou36O closed 3 months ago

Midou36O commented 5 months ago

image It just softlocks here

ReactOS debug log

(win32ss/gdi/gdi32/objects/text.c:576) GdiBCExtTextOut nothing
(win32ss/user/ntuser/windc.c:750) err: [000B0166] GetDC() without ReleaseDC()!
(win32ss/user/ntuser/windc.c:750) err: [000B0166] GetDC() without ReleaseDC()!
(win32ss/user/ntuser/windc.c:750) err: [000B0166] GetDC() without ReleaseDC()!
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(ntoskrnl/ob/obwait.c:441) Failed to reference the handle with status 0xc0000008
(win32ss/user/ntuser/msgqueue.c:2348) err: MQ Cleanup Post Messages E197DCF0
CFSFolder.cpp:988: Unexpected failure (hr)=80004002.
(dll/win32/kernel32/client/version.c:140) VerifyVersionInfo -- Version mismatch(6.-1.-1:-1)
(win32ss/user/ntuser/winpos.c:3525) err: NtUserSetWindowPos bad window handle!
(win32ss/user/ntuser/winpos.c:3525) err: NtUserSetWindowPos bad window handle!
(win32ss/user/ntuser/winpos.c:3525) err: NtUserSetWindowPos bad window handle!
(win32ss/user/ntuser/winpos.c:3525) err: NtUserSetWindowPos bad window handle!
(win32ss/user/ntuser/winpos.c:3525) err: NtUserSetWindowPos bad window handle!
err:(dll/win32/msafd/misc/dllmain.c:1980) Async Connect UNIMPLEMENTED!
(win32ss/gdi/gdi32/objects/text.c:576) GdiBCExtTextOut nothing
(dll/win32/kernel32/client/version.c:140) VerifyVersionInfo -- Version mismatch(6.-1.-1:-1)
fixme:(dll/win32/msafd/misc/stubs.c:84) WSPConnectEx is UNIMPLEMENTED!
iProgramMC commented 5 months ago

I did test out ReactOS and I knew it was having issues. At one point I saw it spike up CPU usage to 100%. I don't know how to debug nor fix this, while I have developed hobbyist OSes before, ReactOS is not my area of expertise.

If you would like to file a pull request to implement the functions ROS says are unimplemented, that would be awesome.

Midou36O commented 5 months ago

Seems like This PR from ReactOS will solve this problem once It gets merged.

iProgramMC commented 5 months ago

Woo! Can't wait!

iProgramMC commented 5 months ago

@zero3k Please don't write comments just to delete them. image

And think before commenting. I've had just about enough, I'm definitely considering blocking you from this org.

iProgramMC commented 3 months ago

Update: It seems compatibility issues with ReactOS have been fixed. Asynchronous connections are a no-go for now. I disabled I/O completion port use and it seems to work. image