jetcam thread race - read thread and processing thread

[PhilipsKoshy]

with camera.running = True, jetcam spawns a thread which reads into camera.value

Now let's say we do, new_image = change['new'] and do some processing. I guess Python does shallow copying and only assigns a reference to the original image array in the new_image variable. So, effectively, new_image and camera.value are pointing to the same memory region. Lets say my processing-thread takes a very long time. In the mean time, camera.value is updated by jetcam-thread. This can cause a thread race. Is that right?