[CDRIVER-2793] Crash observed when destroying client Created: 10/Aug/18 Updated: 30/Aug/18 Resolved: 30/Aug/18 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | None |
| Affects Version/s: | 1.12.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Arun Muralidharan | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 16 64 bit |
||
| Description |
|
We have an application which writes records to a remote MongoDB. On observing connection loss to the remote, we destroy the mongo client and create a new one only the remote connection is established back.
The code for destroying the client is:
Is there something wrong with my destroy sequence ? |
| Comments |
| Comment by A. Jesse Jiryu Davis [ 30/Aug/18 ] | ||||||||||||
|
Hi, let us know if you can provide the debug-build stack trace, otherwise we'll close the ticket for now. | ||||||||||||
| Comment by A. Jesse Jiryu Davis [ 10/Aug/18 ] | ||||||||||||
|
Hi, we don't know of any bugs related to mongoc_client_destroy. Your shutdown sequence looks correct to me. If you rebuild libmongoc with debug symbols enabled (do cmake -DCMAKE_BUILD_TYPE=Debug) and reproduce the bug again you should get a more informative stack trace. | ||||||||||||
| Comment by Arun Muralidharan [ 10/Aug/18 ] | ||||||||||||
|
So, the stack trace is not consistent. This is a new backtrace that I have got.
Looks like some corruption happening. Another thing that I forgot to mention is that, the client destroy is not called as soon as the MongoDB on the remote goes down. There might be some delay before client destroy is called. | ||||||||||||
| Comment by Arun Muralidharan [ 10/Aug/18 ] | ||||||||||||
|
Connection URI is mongodb://10.64.205.22:8006/?ssl=true&connectTimeoutMS=1000 |