[SERVER-66748] AddressSanitizer: heap-use-after-free src/mongo/db/operation_context.h:175:14 in mongo::OperationContext::getServiceContext() const Created: 25/May/22 Updated: 27/Oct/23 Resolved: 31/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Morilha (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 178 | ||||
| Description |
|
heap-use-after-free in Operation Context while executing db_s_config_server_test @ rhel80-debug-aubsan-lite-required (Base commit: d79ef77) |
| Comments |
| Comment by Marcos José Grillo Ramirez [ 01/Jun/22 ] |
|
Correct, it was caused by the initial commit, the changes in SERVER-64433 implied using an operation context on a callback, and now that we're using transactions for removing a shard, that callback could be called after the function in the observer went out of scope. The fix for BF-25280 should also work for the address sanitizer error. |