RE: Inquisit Runtime Window 0 Freeze

Back

Inquisit Runtime Window 0 Freeze

Author	Message
jeff.smith	jeff.smith posted 9 Years Ago Topic Details Share Topic
Group: Forum Members Posts: 33, Visits: 190	Firstly, this is likely a Windows issue and not an Inquisit issue. I am looking for feedback/thoughts. Has anyone else (on an Enterprise version of Windows 7 preferably with no control over updates/admin rights) experienced the "Inquisit Runtime Window 0" as labelled in Task Manager freezing on script abort? E.g. using the http://www.millisecond.com/download/library/Tutorials/ Consent Form Demo, selecting 'disagree' aborts the script, but a blank window hangs and cannot be aborted using Ctrl + Q. A force shutdown must be completed using Task Manager (Ctrl + Alt + Del) on the Consentform.script.iqx. Aborting the Inquisit Windows Runtime 0 also works, but after waiting for a time for Task Manager to identify the Runtime as 'Not Responding'. I did not have this issue last week, however it is a new week and it is possible Windows Update ran and now some sort of conflict is occurring. More details: A data file is created with the disagree response. ConsentformScript.iqx properly loads in Task Manager as well on script abort, but cannot be accessed as the frozen Runtime screen prevails. The issue only occurs for "script.abort();" and there is no hanging/freezing when the survey is completed and ends without a "script.abort();" (e.g. selecting Agree for the ConsentformScript). Ciao for now, Jeff
	Reply Like 33
jeff.smith	jeff.smith posted 9 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 33, Visits: 190	Can't find a way to edit post above... Here is an update. The Runtime Window does not freeze if I first open the script with the "Edit" button, Run from Inquisit toolbar, and select the response that results in script.abort. The Runtime window freezes if I open the script, select Run from the Subject and Group Codes prompt, and select the response that results in script.abort. Jeff
	Reply Like 32
Dave	Dave posted 9 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 105K	Hmm, this actually does sound like an Inquisit bug. Quick question: Have you updated your system to 5.0.1.0 yet (if not, please do so and check if the problem persists) or are you still using 5.0.0.0? Thanks.
	Reply Like 26
jeff.smith	jeff.smith posted 9 Years Ago ANSWER Post Details Share Post
Group: Forum Members Posts: 33, Visits: 190	Yes, it is 5.0.1.0 System Info: Version: 5.0.1.0 32bit (build 3576) Build Date: Mar 31 2016 Build Time: 16:04:25 Expiration Date: Registered Computer Key: (Withheld) Registration Key: (Withheld) Platform: Windows NT 6.1; Win32 CPU Speed: 2294 Memory: 1253 KB available of 2987 KB total Timer resolution: 0.0004462438981724973 milliseconds IP address: (Withheld) MAC address: (Withheld) Graphics Engine: Direct2D Videosync support: DXGIWaitForVBlankMode Dispay 1: \\.\DISPLAY1 Color resolution: 32 bits per pixel Display mode: 1366 x 768 Refresh Rate: 60 Hz Dispay 2: \\.\DISPLAY2 Color resolution: 32 bits per pixel Display mode: 1920 x 1080 Refresh Rate: 60 Hz
	Reply Like 27
Dave	Dave posted 9 Years Ago ANSWER Post Details Share Post
Group: Administrators Posts: 13K, Visits: 105K	Thanks for the detailed report & update. Definitely a bug; unfortunately I can't think of any workaround in case you need to terminate an entire <batch> of scripts. If only a single script is involved, you could use /stop and/or /skip attributes as an alternative to script.abort().
	Reply Like 31