[SERVER-31118] Crash on OpenBSD with malloc.conf -> SURFg Created: 17/Sep/17  Updated: 29/Jan/18  Resolved: 18/Sep/17

Status: Closed
Project: Core Server
Component/s: Security, Stability
Affects Version/s: 3.2.7
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jesper Wallin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tested on OpenBSD 6.1 and 6.2-beta.


Attachments: File mongocrash.log    
Issue Links:
Duplicate
duplicates SERVER-29083 [ftdc] Invalid access at address Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:
  1. ln -s 'SURFg' /etc/malloc.conf
  2. /etc/rc.d/mongod start
Participants:

 Description   

On OpenBSD, you can configure malloc.conf to detect bugs like use-after-free, providing junked memory, etc. When using malloc.conf configured with SURFg (S adds CJ) my MongoDB server crashes right after start. Both with and without any data in the datadir.



 Comments   
Comment by Mark Benvenuto [ 18/Sep/17 ]

This is a duplicate of SERVER-29083. You can apply the patch below from master to fix the issue.

https://github.com/mongodb/mongo/commit/f0e1e116322917c83e0c1d11b56afa088fe6ccd7

Generated at Thu Feb 08 04:26:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.