0
Searching answer

Can FixInsight handle concurrency?

Lübbe Onken 10 years ago updated 10 years ago 4

On our buildserver, which runs up to four build jobs in parallel, we recently had a few FixInsight failures with exit code 255. What does this exit code mean?

Is it possible that two (or more) instances of FixInsight running at the same time can get into each others way?

Searching answer

It should work fine, command line process doesn't use any shared resources.

In a normal situation it can only return 0,1 or 2 exit code. I guess 255 means that it has been interrupted by some OS exception.


Can you please turn on Debug Mode (a check box in about dialog) and send me a log after a fail?

Hi Roman,

I kept an eye on failed builds in the past weeks and this particular failure hasn't happened again. When it happened, the build server was grinding non-stop.

How would I turn on the debug mode without a GUI? Is there a command line option or registry entry?

Hi Lübbe,


Look at HKEY_CURRENT_USER\SOFTWARE\FixInsight

Create (or edit) key DebugMode (REG_DWORD)

0x1 = Debug Mode On

0x0 = Debug Mode Off


Damn, it's again for current user. I think I should move all settings to HKEY_LOCAL_MACHINE. What do you think?

It would be great, yes. But then you have to offer an "Install for all users/current user only" choice in the setup. People who don't have admin rights during installation can't install for all users. So you still have to be able to find your settings in both cases.