Inquisit 4 Crashing when Opened

asali — Wed, 25 Mar 2020 15:45:02 GMT

Hello. I've been using Inquisit for about a year and just today started having problems opening the app. I'm currently running Mac OS 10.13.6. The problem started immediately after I installed a Mac security update. When I open Inquisit now, the program crashes and gives me the message I've pasted below. My institution only has a license for Inquisit 4, but I tried installing Inquisit 5 and doing the free trial. Inquisit 5 does not seem to have this issue. Unfortunately, I need version 4 to work for this study. I also tried reinstalling version 4 and when I do so, the installer fails partway through with the same error message. Is this a known issue and is there a fix? Thank you so much for your help!

Process:     Inquisit [1187]
Path:      /Applications/Inquisit.app/Contents/MacOS/Inquisit
Identifier:    com.millisecond.Inquisit
Version:     ???
Code Type:     X86-64 (Native)
Parent Process:   ??? [1]
Responsible:    Inquisit [1187]
User ID:     502

Date/Time:     2020-03-25 10:54:17.489 -0400
OS Version:    Mac OS X 10.13.6 (17G12034)
Report Version:   12
Bridge OS Version: 3.0 (14Y901)
Anonymous UUID:   354FC08B-725B-D027-1B3A-31247A0581DC

Time Awake Since Boot: 3200 seconds

System Integrity Protection: enabled

Crashed Thread:   0

Exception Type:   EXC_CRASH (Code Signature Invalid)
Exception Codes:   0x0000000000000000, 0x0000000000000000
Exception Note:   EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2):
-->
__TEXT      0000000100000000-0000000100fd9000 [ 15.8M] r-x/rwx SM=COW M []

Thread 0 Crashed:
0 ???             0x0000000108c4a19c _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffeefbffbe0
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x0000000108c4a19c rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0
Error Code:  0x00000000
Trap Number: 0

Binary Images:
   0x100000000 -   0x100fd8ff7 +??? (???) <0BF6B971-D2FF-3677-914D-40E3758F6F82> (null)
   0x108c49000 -   0x108c93adf +??? (551.5) <ACC6AC7F-EAD9-340E-B2A8-AD26FE5B387B> (null)

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 3673
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=19.6M resident=0K(0%) swapped_out_or_unallocated=19.6M(100%)
Writable regions: Total=8432K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8432K(100%)

           VIRTUAL REGION
REGION TYPE        SIZE COUNT (non-coalesced)
===========       ======= =======
STACK GUARD        56.0M   2
Stack          8192K   2
__DATA          792K   5
__LINKEDIT        3560K   3
__TEXT          16.1M   3
shared memory        8K   3
===========       ======= =======
TOTAL          84.4M   12

RE: Inquisit 4 Crashing when Opened

Dave — Wed, 25 Mar 2020 15:45:02 GMT

+x[quote]

[b]asali - 3/25/2020[/b]
Hello. I've been using Inquisit for about a year and just today started having problems opening the app. I'm currently running Mac OS 10.13.6. The problem started immediately after I installed a Mac security update. When I open Inquisit now, the program crashes and gives me the message I've pasted below. My institution only has a license for Inquisit 4, but I tried installing Inquisit 5 and doing the free trial. Inquisit 5 does not seem to have this issue. Unfortunately, I need version 4 to work for this study. I also tried reinstalling version 4 and when I do so, the installer fails partway through with the same error message. Is this a known issue and is there a fix? Thank you so much for your help!

Process:     Inquisit [1187]
Path:      /Applications/Inquisit.app/Contents/MacOS/Inquisit
Identifier:    com.millisecond.Inquisit
Version:     ???
Code Type:     X86-64 (Native)
Parent Process:   ??? [1]
Responsible:    Inquisit [1187]
User ID:     502

Date/Time:     2020-03-25 10:54:17.489 -0400
OS Version:    Mac OS X 10.13.6 (17G12034)
Report Version:   12
Bridge OS Version: 3.0 (14Y901)
Anonymous UUID:   354FC08B-725B-D027-1B3A-31247A0581DC

Time Awake Since Boot: 3200 seconds

System Integrity Protection: enabled

Crashed Thread:   0

Exception Type:   EXC_CRASH (Code Signature Invalid)
Exception Codes:   0x0000000000000000, 0x0000000000000000
Exception Note:   EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2):
-->
__TEXT      0000000100000000-0000000100fd9000 [ 15.8M] r-x/rwx SM=COW M []

Thread 0 Crashed:
0 ???             0x0000000108c4a19c _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007ffeefbffbe0
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x0000000108c4a19c rfl: 0x0000000000000200 cr2: 0x0000000000000000

Logical CPU: 0
Error Code:  0x00000000
Trap Number: 0

Binary Images:
   0x100000000 -   0x100fd8ff7 +??? (???) <0BF6B971-D2FF-3677-914D-40E3758F6F82> (null)
   0x108c49000 -   0x108c93adf +??? (551.5) <ACC6AC7F-EAD9-340E-B2A8-AD26FE5B387B> (null)

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 3673
thread_create: 0
thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=19.6M resident=0K(0%) swapped_out_or_unallocated=19.6M(100%)
Writable regions: Total=8432K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8432K(100%)

           VIRTUAL REGION
REGION TYPE        SIZE COUNT (non-coalesced)
===========       ======= =======
STACK GUARD        56.0M   2
Stack          8192K   2
__DATA          792K   5
__LINKEDIT        3560K   3
__TEXT          16.1M   3
shared memory        8K   3
===========       ======= =======
TOTAL          84.4M   12

[/quote]

It's not clear this is actually an issue with the Inquisit.app or an OSX malfunction. The crash occurs due to a signature verification failure. If you google the error, you'll find that random applications seem to be affected by this, especially shortly after the OS installed an update or upgrade, and there's no real rhyme or reason for why that happens and how to fix it.

(https://www.literatureandlatte.com/forum/viewtopic.php?p=287365&sid=81c1d792f1034950df2850db40301f03#p287365 sums it up nicely.)

Some people report having had luck with booting into safe mode, starting an affected app there, and after that it functioned again when booting the OS normally, too. Others have reported having to re-install or upgrade the OS.

Millisecond Forums » Millisecond Forums » Inquisit 4 » Inquisit 4 Crashing when Opened

Inquisit 4 Crashing when Opened

RE: Inquisit 4 Crashing when Opened