[SERVER-45238] Some unit tests have massive memory leaks when built with VS2019 Created: 18/Dec/19  Updated: 29/Oct/21  Resolved: 24/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45593 ClockSource::waitForConditionUntil ca... Closed
Duplicate
duplicates SERVER-45593 ClockSource::waitForConditionUntil ca... Closed
Operating System: ALL
Steps To Reproduce:

> c:\python\Python37\python.exe ./buildscripts/scons.py --dbg=on --opt=on --win-version-min=win10 --jlink=1 MSVC_VERSION=14.2 build\optdebug\mongo\util\util_test.exe
> build\optdebug\mongo\util\util_test.exe

Watch under performance tools to see the memory growth, which is very rapid. You will want to ^C that before it eats all your memory.

Sprint: Dev Platform 2020-02-10
Participants:

 Description   

While experimenting with VS2019 for faster builds, we ran the unit tests and found that they terminated via OOM.

Some initial investigation suggested misbehavior in the alarm subsystem, but we didn't dig too much further.

It is possible that it is another manifestation of https://developercommunity.visualstudio.com/content/problem/861451/possible-codegen-issue-after-attempting-to-upgrade.html, but in case it is not, I'm filing the ticket to track it.



 Comments   
Comment by Andrew Morrow (Inactive) [ 15/Jan/20 ]

And we have an RCA now after a day of debugging, in SERVER-45593.

Comment by Andrew Morrow (Inactive) [ 15/Jan/20 ]

MS released VS 2019 16.4.3, but it did not fix this issue.

Generated at Thu Feb 08 05:08:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.