**System Information**
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069
**Blender Version**
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `rBf6cb5f54494e`
(also tried on the latest 2.81 Beta)
Worked: (optional)
**Short description of error**
I don't think it's a bug, but rather something that hasn't been thought of. Currently when you use Cryptomatte and export an OpenEXR Multilayer file, if you then import it into the compositor and change its color space to something other than linear, the cryptomatte passes will also be affected by the color space change and will no longer work properly.
**Exact steps for others to reproduce the error**
Use any blender scene, enable cryptomatte, and render a 1 frame animation in OpenEXR Multilayer.
Import the file in the compositor, connect it to a cryptomatte node.
Change the color space of the file to linearACES for example.
Then try color picking the cryptomatte passe.
It will behave very weirdly, sometimes you will not be able to select an object, or the edges of the matte will not be antialiased etc.
Sorry for being so vague about the exact steps to follow to reproduce the bug but it is quite simple to recreate.