We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
@nathan_k can you please post the log starting from the stack dump entry up to the error entry or better just send me the whole log.
@glenn I haven't cleared the log in a while, so you get a years worth.
ok, it goofed off and the debug log is attached. Not sure it's helpful though.
Thanks for that.
cmd2 appears to be the powershell command to get the wifi info. apparently it takes 103 seconds to complete *and then* throws a timeout error. I don't see a thread-timeout option in the config so it shouldn't be triggering a timeout. This is most interesting. It tells me there is potential for the thread to be accessed and/or destroyed after it has completed but before the thread itself has signalled it has ended. Meaning invalid pointers.
The other question is, why is powershell taking 103 seconds to return?
I see the code is setting a default timeout regardless of whether the option exists or not. I will change this to only set the timeout if the process is marked as threaded.
There's also a line that needlessly retrieves the item pointer from a potentially destroyed thread. This could send the main thread into la-la land given the right circumstances. I'll remove this.
