[SERVER-749] mongod prints ugly _context should be NULL message on shutdown in windows Created: 15/Mar/10  Updated: 28/Jun/12  Resolved: 11/May/10

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

Type: Bug Priority: Minor - P4
Reporter: Aaron Staple Assignee: Mathias Stearn
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Seen in tool test runs, possibly it occurs in other contexts as well.

<http://buildbot.mongodb.org/builders/Windows%2064-bit/builds/485/steps/test_1/logs/stdio>

m31000| Mon Mar 15 13:45:14 closeAllFiles() finished
m31000| Mon Mar 15 13:45:14 dbexit: really exiting now
m31000| ERROR: Client::~Client _context should be NULL



 Comments   
Comment by Mathias Stearn [ 11/May/10 ]

I cant reproduce on my XP VM and I don't see the error in buildbot any more.

Comment by Eliot Horowitz (Inactive) [ 15/Mar/10 ]

true - if you can figure it out - that'd be great

Comment by Aaron Staple [ 15/Mar/10 ]

Yeah probably harmless, I was just thinking that if I didn't know mongo well a random error message on shutdown wouldn't exactly inspire confidence.

Comment by Eliot Horowitz (Inactive) [ 15/Mar/10 ]

harmless i think

Comment by auto [ 15/Mar/10 ]

Author:

{'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}

Message: debugging for SERVER-749
http://github.com/mongodb/mongo/commit/d3c36d8e6c9ec00b6c7656b861034e7240340fa5

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