[SERVER-76755] RecordId self reference assignment can lead to segfault Created: 02/May/23  Updated: 29/Oct/23  Resolved: 10/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jordi Olivares Provencio Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-81976 Fix RecordId GDB pretty printer Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-05-15
Participants:

 Description   

This is currently the case with the change collection remover that's not yet enabled. We should either avoid that or decide if it's worth adding the extra overhead into the operator= of RecordId.



 Comments   
Comment by Githook User [ 09/May/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-76755 Fix self-assignment errors with truncate markers
Branch: master
https://github.com/mongodb/mongo/commit/c2a2e417e42e80e7d9c800a2940281ad085282d2

Generated at Thu Feb 08 06:33:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.