milvus: [Bug]: fatal error: unexpected signal during runtime execution

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version:2.0.0
- Deployment mode(standalone or cluster): standalone
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus v2.0.0
- OS(Ubuntu or CentOS):  Ubuntu
- CPU/Memory: inteli7/32gb
- GPU: -
- Others: default milvus settings. 
- - "index_type": "IVF_FLAT", "nlist": 100, "metric_type": "IP".
- - there are 2 collections in DB: each <50k rows, each row consists of id and 256dim vector.

Current Behavior

Milvus unpredictable exits docker container while ANN searching. I tried around 10 times, always different quantity of searches is needed to milvus be exited. On average after ~200 consequtive searches milvus will be exited. Each search spends around 0.2sec.

Expected Behavior

I expected Milvus will work infinitely 😃

Steps To Reproduce

1. fresh standalone milvus docker up with default milvus settings. 
2. create 2 collections.
3. fulfill with data:<50k rows, each row consists of id and 256dim vector.
4. create index "index_type": "IVF_FLAT", "nlist": 100, "metric_type": "IP".
5. conduct 100+ times consequently this: 
5.1. search in first collection, take IDs
5.2. search in second collection with expr="id in IDs".
6. Somewhere here you will get "fatal error: unexpected signal during runtime execution" + exited milvus with super-long log output.

Anything else?

No response