[SERVER-19441] On out of memory condition we should issue a dump file before an attempt to format the problem to mogod logfile Created: 16/Jul/15  Updated: 03/Feb/16  Resolved: 17/Nov/15

Status: Closed
Project: Core Server
Component/s: Diagnostics, Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eitan Klein Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: 32qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File Trace.log    
Participants:

 Description   

On a single replica set mongod or SA

Version:
db version v3.1.6-pre-
git version: 63863aefa21b33e6f84b8b466f70581dd921dba7
OpenSSL version: OpenSSL 1.0.1p-fips 9 Jul 2015

Environment: Windows

When machine get to out of memory condition, we don't have the resources to format the symbols and print the problem to our trace file (required additional load module and string allocations...).

It will be better if we will issue the dump before trying to format, this will help us to understand the problem

currently implementation

printWindowsStackTrace(contextCopy);
doMinidumpWithException(excPointers);

i suggest to switch the order minidump should be first


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