I downloaded the new IDE, version 1.9.0, and sometimes when I click on the stop button (the red X), instead of stopping, the camera LEDs all turn on (white) and the IDE doesn't respond. Eventually the OS reports that the device was removed. I'm on macOS High Sierra. Anyone else having any problems?

Hi, we updated the IDE software to add more timeouts for Mac. We found this to be the issue with the camera having problems. We wait 50 ms after the last polling command sent the camera on Mac to issue stop and 50 ms afterwards. Does this issue happen every time? Getting all white LEDs means a fatal error.

I get this problem fairly regularly. Hit the stop cross and I get a white light on my M7. OS sees the M7 as disconnected. Sometimes I get a corrupt SD card. I am assuming that the IDE exception that you get is interrupting a file IO operation hence the SD card corruption.
It would be nice if there were some way of of flagging to a script that a halt has been requested. Then the script could terminate gracefully under program control.
I am looking at attaching some switches to the M7 GPIO so that an ISR can set a flag that my scripts can use to terminate gracefully with. Instead of a while(True) statement I can then use a while(<flag not set>).
Much nicer if this could be implemented in some way through the IDE
I am using IDE V1.9.0, OS is Linux (openSUSE Leap 42.2).

Ok. The code i am using is as below
Note that all the io is happening because i was tracking down why the image held in the allocated frame buffer was getting corrupted.
I suspect that one of the routines, such as find_blobs, is using the memory without checking to see if it is in use.
That is just a theory.
The code may not make a lot of sense as this is a snapshot of where I am in my current investigations.
The overall task is to detect movement and to save a clean image of the frame where movement was detected.
I found in my use case your method of using percentiles did not work very well

Hi, we just got a bug report of a pointer possibly not being checked in our list code from another user and this causing an issue. The problem is like in find blobs. The weird thing is... This issue would have been in the firmware for years now and yet the method appears to work still.

Anyway, I'm at Maker Faire today and this weekend but I can get this fixed if it's and issue with find blobs. Ibrahim may jump in if he can.

I don't get this every time. Actually, today was going pretty well but the IDE wasn't recognizing the camera and I created a new file and ran it when all the LEDs came on again. So, I don't think it is related to find_blobs in my case.

In fact, I saved the default "new" file and was able to get it to fail on the first time of resetting the camera and running it.