[SERVER-17105] Server fails to start under Valgrind: 'Failed to set tcmalloc.max_total_thread_cache_bytes' Created: 28/Jan/15  Updated: 17/Nov/15  Resolved: 12/Nov/15

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 3.0.0-rc7
Fix Version/s: 3.2.0-rc3

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-16829 Expose tcmalloc runtime configuration... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platform C (11/20/15)
Participants:

 Description   

This looks like fallout from SERVER-16829.

$ valgrind --tool=memcheck --num-callers=35 --soname-synonyms=somalloc=NONE --suppressions=./valgrind.suppressions ./mongod
 
==12366== Memcheck, a memory error detector
==12366== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==12366== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==12366== Command: ./mongod
==12366== 
2015-01-28T18:13:28.584-0500 F CONTROL  Failed global initialization: InternalError Failed to set internal tcmalloc property tcmalloc.max_total_thread_cache_bytes


Version: ac9ee2fb80f2af



 Comments   
Comment by Githook User [ 12/Nov/15 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-17105 Valgrind 3.11.0 Import
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/e81e6cb7c8df17f95f9aae50c3a681bf27acffaa

Comment by Githook User [ 12/Nov/15 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-17105 Check for running under Valgrind
Branch: master
https://github.com/mongodb/mongo/commit/0d345a87c62fed483103c684d91901d0c5d424af

Comment by Githook User [ 12/Nov/15 ]

Author:

{u'username': u'markbenvenuto', u'name': u'Mark Benvenuto', u'email': u'mark.benvenuto@mongodb.com'}

Message: SERVER-17105 Valgrind 3.11.0 Import
Branch: master
https://github.com/mongodb/mongo/commit/0c25b468fd93fb86c010d3bcaeab81c2e59ae2fe

Comment by Andrew Morrow (Inactive) [ 08/Oct/15 ]

This should, and previously did, work. I think what is needed here is a runtime check for "running under valgrind" that elides any calls to the tcmalloc management and configuration APIs. In particular, the RUNNING_ON_VALGRIND function documented here: http://valgrind.org/docs/manual/manual-core-adv.html.

Comment by Andy Schwerin [ 08/Oct/15 ]

acm, do we support valgrind with any allocator other than the system allocator?

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