May 12 2016, 2:55 pm
|
|
Lummox JR
  |
What happens if you disable Aero?
|
Ummm... I'm on Windows 10, i don't use Aero : P
| |
The reason I asked about Aero is that the extended stack trace shows a lot of uxtheme calls--not necessarily in the call stack proper, but they were obviously called at some point. So if it's not Aero, it might be whatever theme you are using.
Gathering more dump files would probably help, along with the version number used at the time so it can be checked. | |
The version i was using is 510.1340. Please tell me: I should gather more dumps when it's frozen? I'm sure it will only yield the same results...
This also happens in every version i tried to 509 to 510. | |
Nopm wrote:
The version i was using is 510.1340. Please tell me: I should gather more dumps when it's frozen? I'm sure it will only yield the same results... I think a good next step might be theme-related, as he mentioned- are you using some kind of custom theme on Windows 10, or is it all stock? You might consider, if you've customized it, reverting back to defaults for a bit and see if you can still reproduce it. | |
It's not "customized", i've just changed colors and enabled transparency, it's probably not the issue... Although i did change the white color (vanilla) using a 3rd party tool... I will check, thanks! (Still i don't think it's the issue though)
| |
Yeah, fair enough. Does the third party tool require itself to be running (background or otherwise) for the color to remain in effect, or does it just do some kind of registry/config magic?
The main concern there would be if it's fooling around with some of the win32 api crud and somehow borking the state in a way that may not be expected from BYOND's perspective. | |
Audeuro wrote:
The main concern there would be if it's fooling around with some of the win32 api crud and somehow borking the state in a way that may not be expected from BYOND's perspective. With one of those dumps getting caught in a SetRedraw(FALSE) call, that actually makes perfect sense. | |
It's that Ultimate Windows Customizer thing, no, it doesn't run in background. I will disable it.
| |
Nope, didn't fix shit. I guess it was not a issue with that.
| |
Did you reboot after you disabled it?
| |
Of course i did. Didn't work.
| |
ummm... Bump?
| |
Did you really just bump a 1 day response?
| |
At the very least I need more data on this. I'm thinking there has to be something on your system causing this, at least based on the fact that the current stack traces you've got don't point to anything in DS's code being the cause.
| |
Could you specify which data? I'll happily give you anything that can help.
| |
More dump files with stack traces, basically. The 510 one yielded no clues, and the 509 one points to something theme-related on your system. (I know you've since disabled that, but the fact of its existence has me wondering what else might be lurking out there.)
| |
Besides dumps on DS, do i need to stack trace something else? If yes, what?
| |
No, since it's DS that's hanging I think that's the only stack trace that would be of any use. And to be honest I don't know if new stack traces will tell me anything, but that's the only kind of data I can think to gather--short of getting a full list of all the processes running on your system (which might still have merit).
| |