Fix Errors or Slow Polyspace Runs from Disk Defragmentation and Anti-virus Software

Issue

In some cases, anti-virus software checks can noticeably slow down a Polyspace® analysis. This reduction occurs because the software checks the temporary files produced by the Polyspace analysis.

You see noticeably slow analysis for a simple project or the analysis stops with an error message like the following:

Some stats on aliases use: 
  Number of alias writes:      22968 
  Number of must-alias writes: 3090 
  Number of alias reads:       0 
  Number of invisibles:        949 
Stats about alias writes: 
  biggest sets of alias writes: foo1:a (733), foo2:x (728), foo1:b (728) 
  procedures that write the biggest sets of aliases: foo1 (2679), foo2 (2266),
                                                             foo3 (1288) 
**** C to intermediate language translation - 17 (P_PT) took 44real, 44u + 0s (1.4gc) 
exception SysErr(OS.SysErr(name="Directory not empty", syserror=notempty)) raised. 
unhandled exception: SysErr: No such file or directory [noent] 


-------------------------------------------------------------------------- 
---                                                                    --- 
---  Verifier has encountered an internal error.      --- 
---  Please contact your technical support.          --- 
---                                                                    --- 
---------------------------------------------------------------------------

Possible Cause

A disk defragmentation tool or anti-virus software is running on your machine.

After starting an analysis, check the processes running and see if an anti-virus process is causing large amount of CPU usage (and possibly memory usage).

Solution

Try:

  • Stopping the disk defragmentation tool.

  • Deactivating the anti-virus software. Or, configuring exception rules for the anti-virus software to allow Polyspace to run without a failure.

    For instance, you can try the following:

    • Configure the anti-virus software to allow the Polyspace executables.

      For instance, in Windows®, with the anti-virus software Windows Defender, you can add an exclusion for the Polyspace installation folder C:\Program Files\Polyspace\R2019a, in particular, the .exe files in the subfolder polyspace\bin and the .exe files starting with polyspace in the subfolder bin\win64 (for instance, polyspace-internal-connector.exe).

    • Configure the anti-virus software to exclude your temporary folder, for example, C:\Temp, from the checking process.

      See Storage of Temporary Files During Polyspace Analysis.