May i bump this? It's been a few days already
| |
I don't see anything that ends in byondwin.dll or byondcore.dll code. Did you in fact keep track of where you were at each point when you used gu? You didn't post anything about the last stack trace info (from the "k" command) prior to it hanging again.
| |
This is getting weird, because i had CLEARLY seen byondwin.dll in the stack trace, after that i "gu"ed all the way until it looped, then i traced it again. Why aren't you seeing the byondwin i wonder?
| |
I see it in the trace, but it's not the most recent item in the trace. What I need to know is, what did the stack look like just before your last "gu" caused it to loop again?
| |
To explain this another way, let's say your stack trace looks like this:
G F E D C B A Assume that C is the one that's the cause of the loop. As you "gu", you'll go up so G pops off, then F, then E, D, and you should then get to C. Then the next time you use "gu", it goes back to looping infinitely because C is the one that's stuck. But when you stop at that point, the stack may look like this again: F E D C B A And from there it's not clear what's wrong. So what I need is to see the stack trace, how it looked when you were at C but hadn't yet done that last "gu" command. | |
I'm gonna take a screenshot then, because this is melting my brain. (Will that work?)
| |
Bump again :3
| |
I can't move forward without the information I asked for.
1) Get the application into a state where it hangs. 2) Open it in WinDbg. 3) Switch to thread 0 (or whichever is appropriate). 4) Get a stack trace. 5) Copy it down somewhere, like in Notepad. 6) Use the "gu" command. If it succeeds, return to step 4. If it hangs, the last stack trace points to where the program is actually hanging. 7) Paste all of the stack traces you got. | |
I had to delete a reply since one of the .txt i had posted contained repetitive stacks.
| |
So here is a dump of all the stacks i've got: http://puu.sh/pvKtD/5feed48c42.dmp
And here is a .txt file with all of them in the order i took them (until the "gu" hang): http://puu.sh/pvKvW/b9a11c3eae.txt | |
Something truly weird is happening here, but based on the fact that ClientCallWinEventProc() appears to be where it hangs, and that you're seeing stuff like OnAppChanged() and registry access, this leads me to believe that something on your system is hooking the richedit control, or at least some of the messages being sent to it.
What does your full process list look like in the task manager? And have you run a virus scan at all recently? I would not be surprised to find malware at work in your case. | |
Malware? Nah, a lot of Windows 10 users have this same issue, and it isn't malware. And the process list: http://puu.sh/pykaw/a5a304ca6b.txt
| |
You mentioned RichEdit control... Dou you have an idea of what could hooking it? I mean, i got a lot of crap running on my PC. If you give me an idea of what can hook it, i may be able to resolve this. But as i said earlier, i tested that code you've sent me and the text was shown fine, no freezes. I guess it's something more complex than that.
| |
launch DS, open up ProcessExplorer (google and download it if need be) (as admin if you can)
select DS in ProcessExplorer and go to view -> lower plane view -> show dlls select everything and copy paste to pastebin and link it here That will tell us what is hooking in | |
Here is a list of the dlls i saved with Process Hacker:
http://puu.sh/pyZVF/b923297617.txt I don't know if it's enough though! | |
process explorer tells you the full path, and its a program released by a company microsoft owns, so its trustworthy
edit, wait a moment, you used to be able to copy and paste from that field. hmm edit2: sort by path, expand it up higher, and just screen shot it i guess | |
Yeah i know, i use it only for things Process Hacker does not do, which is very few things. Thanks for the opinion though! Now, changing topic, i really do hope that DLL list helps with something.
| |
the dll list isn't as helpful because it does not contain the full path of the dll.
| |
http://puu.sh/pz1oq/4da7e3faab.txt Here, now with Process Explorer.
| |
And SURPRISNGLY it didn't hang using the test code... curious.