OpenCV/Numpy example not working correctly on macOS

Hi, First of all, thank for a great library. I encountered some issues while trying to record my screen.

General informations:

• MSS version: 3.0.1
• OS name: macOS Sierra
• OS version: 10.12.5 (16F73)
• OS architecture: 64 bits
• Result of the command python --version: Python 3.5.3
• OpenCV version: opencv3 : 3.1.0
• Numpy Version: 1.12.1

Description of the warning/error

I tried out OpenCV/Numpy example to record the screen. But the frames are getting delayed with time(exponentially), I think there are lots of GC happening. I interrupted the command line after fps: 0.07140145917730202 because the display window was not responding. Ways to reproduce: It is happening every time.

Full message

Rohits-MacBook-Pro:drive rohitarya$ python3 readscreen.py 
fps: 4.144634697781783
fps: 1.2977357482958785
fps: 0.3543577094166482
fps: 0.07140145917730202
^Cpython3(19339,0x7fffe9aae3c0) malloc: *** mach_vm_map(size=8404176896) failed (error code=4)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
python3(19339,0x7fffe9aae3c0) malloc: *** mach_vm_map(size=8404176896) failed (error code=4)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
python3(19339,0x7fffe9aae3c0) malloc: *** mach_vm_map(size=8404176896) failed (error code=4)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
python3(19339,0x7fffe9aae3c0) malloc: *** mach_vm_map(size=8404176896) failed (error code=4)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
python3(19339,0x7fffe9aae3c0) malloc: *** mach_vm_map(size=8404176896) failed (error code=4)
*** error: can't allocate region

Other Information

Rest of the examples(Part of the screen, PIL, Playing with pixels) are working perfectly fine.

[arpit-kalla]

Kindof solved the issue by putting the monitor = {'top': 40, 'left': 0, 'width': 100, 'height': 100} line inside the loop. Dont know why this exactly works but I assume the monitor values are getting updated by mistake in the grab function

[BoboTiG]

Hello, could you try with the latest version in the dev branch please? I removed the border effect with monitor’s width.