Reply to thread

Message

<blockquote data-quote="TheNoctambulist" data-source="post: 1098937" data-attributes="member: 136501">Hi,I found some free time this weekend and had a look into the disconnect/reconnect and macro problems. The macro problem was easy enough to reproduce, debug, and fix. There was a simple issue with how IRSS was attempting to replace environment variables in the if statements and when setting variable values. I have attached patch IrssVariablesAndIfStatements with a fix for the problem.I was unable to reproduce the problem of 100% CPU usage after disconnecting/reconnecting my MCE transceiver.I also recently started noticing intermittent weirdness with my previous suspend/resume fix where IRSS would sometimes stop working entirely the first time the computer was resumed after a reboot. Strangely, this only happened after reboots that were triggered by PowerScheduler++, but never if I rebooted the PC myself. I eventually tracked it down to a race condition caused by the suspend code still not finishing before the computer went to sleep. This meant that when the computer resumed the suspend code and resume code were running at the same time! I have attached patch IrssSuspendResumeUpdate with a fix for this problem.</blockquote>

[QUOTE="TheNoctambulist, post: 1098937, member: 136501"] Hi, I found some free time this weekend and had a look into the disconnect/reconnect and macro problems. The macro problem was easy enough to reproduce, debug, and fix. There was a simple issue with how IRSS was attempting to replace environment variables in the if statements and when setting variable values. I have attached patch IrssVariablesAndIfStatements with a fix for the problem. I was unable to reproduce the problem of 100% CPU usage after disconnecting/reconnecting my MCE transceiver. I also recently started noticing intermittent weirdness with my previous suspend/resume fix where IRSS would sometimes stop working entirely the first time the computer was resumed after a reboot. Strangely, this only happened after reboots that were triggered by PowerScheduler++, but never if I rebooted the PC myself. I eventually tracked it down to a race condition caused by the suspend code still not finishing before the computer went to sleep. This meant that when the computer resumed the suspend code and resume code were running at the same time! I have attached patch IrssSuspendResumeUpdate with a fix for this problem. [/QUOTE]

Verification