[SERVER-42029] Fix memory management in libunwind backtracer Created: 01/Jul/19  Updated: 29/Oct/23  Resolved: 20/Sep/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Sara Williamson Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to SERVER-42405 Factor out duplicated code between ex... Closed
Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-07-15, Dev Tools 2019-07-29, Dev Tools 2019-08-12, Dev Tools 2019-09-09, Dev Tools 2019-09-23
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 20/Sep/19 ]

Author:

{'name': 'Billy Donahue', 'username': 'BillyDonahue', 'email': 'billy.donahue@mongodb.com'}

Message: SERVER-42029 Combine stacktrace posix and unwind files
Branch: master
https://github.com/mongodb/mongo/commit/668d07c416dfcd62f245211d7f9a74898ece59fb

Comment by Billy Donahue [ 07/Aug/19 ]

https://mongodbcr.appspot.com/478840002/

Comment by Andrew Morrow (Inactive) [ 17/Jul/19 ]

Additional details here:

  • We should probably expand the size of the pre-allocated buffer for the MallocFreeOstream, because 100k is pretty small.
  • We need to make the libunwind walk callback based so that we can write each record into the stream, rather than accumulating all the state on the stack. Right now it uses 500kb which is too much.
Generated at Thu Feb 08 04:59:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.