I seem to have a similar problem with cygwin and CIS/Sandbox as reported in another post.
I followed the hint in that post and added cygwin’s bash.exe to D+'s CSP as an “Installer or Updater”. Problem is that I start cygwin via a small bat file containing nothing but
bash --login -i
It opens a cmd window and executes bash, that’s all. Since I installed CIS 4 this morning, I get the following error message in the cmd window that duly opens:
C:\cygwin\bin\bash.exe: *** fatal error - couln’t allocate heap, Win32 error 487, base 0x…
Even adding cmd.exe as an Installer/Updater (probably not a good idea) did not do the trick.
Did you try to add the batch to “Safe Files” that should get the batch out of the sandbox and also prevent bash.exe from getting sandboxed, because if an untrusted program get’s sandboxed all things it starts will also be sandboxed…
Sorry, I did not make myself understood. The cygwin problem remains, but CIS no longer complaints/notifies about sandboxing the app.
I have just updated my cygwin installation to the latest 1.7 (should now be ok), but still get similar errors when executing the batch file and then issuing commands like ls or gcc: see attached screen shot.
As for CIS, I have the batch file as a safe file and bash.exe as an Installer/Updater in D+ → Advanced.
You’ll probably only receive the Sandbox alert once after reboot, so you’ll probably have to boot fresh to see it again, if that still doesn’t solve the issue, try to disable the sandbox for a moment and see if all works fine then.
If it does I can only think of putting the batch file on CPS also as installer and remove it from Trusted Files, also make sure it’s not on the “pending files” list…