[SERVER-22538] Suppress ASAN leak in ASIO library on unclean shutdown Created: 09/Feb/16 Updated: 21/Mar/18 Resolved: 08/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In ASIO, we new an object, then create a thread and transfer ownership of this object to the new thread. As long as the newly-created thread exits properly then we won't leak this object. If, however, we exit from the database while that thread is still running, ASAN will be unhappy. As there isn't anything we can do about this, and it isn't an ASIO bug, we should suppress this. |
| Comments |
| Comment by Samantha Ritter (Inactive) [ 27/Nov/17 ] |
|
This bug showed up again in a recent test run, so I am re-opening this ticket. |