[SERVER-27064] both mongo and mongorestore report malloc_zone_unregister when starting Created: 16/Nov/16  Updated: 31/May/17  Resolved: 27/Feb/17

Status: Closed
Project: Core Server
Component/s: Shell, Tools
Affects Version/s: 2.6.13
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Ralph Decatrel Assignee: Andrew Morrow (Inactive)
Resolution: Cannot Reproduce Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

see these errors when running mongo and mongorestore:
mongo(821,0x7fffbc3713c0) malloc: *** malloc_zone_unregister() failed for 0x7fffbc367000
mongorestore(1055,0x7fffbc3713c0) malloc: *** malloc_zone_unregister() failed for 0x7fffbc367000

It may be related to the recent upgrade to Sierra.

System information:

Model Name: MacBook Air
Model Identifier: MacBookAir5,2
Processor Name: Intel Core i7
Processor Speed: 2 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB

System Version: macOS 10.12.1 (16B2555)
Kernel Version: Darwin 16.1.0

*brew info mongodb26:

homebrew/versions/mongodb26: stable 2.6.12 (bottled)
High-performance document-oriented database
https://www.mongodb.org/
/usr/local/Cellar/mongodb26/2.6.11 (17 files, 329.2M)
Poured from bottle on 2016-09-20 at 11:28:43
/usr/local/Cellar/mongodb26/2.6.12 (18 files, 314.8M) *
Poured from bottle on 2016-11-16 at 10:59:05
From: https://github.com/Homebrew/homebrew-versions/blob/master/mongodb26.rb
==> Dependencies
Build: scons ✘
Optional: boost ✘, openssl ✔
==> Requirements
Required: macOS >= 10.6 ✔
==> Options
--with-boost
Compile using installed boost, not the version shipped with mongodb
--with-openssl
Build with openssl support

mongod --config /usr/local/etc/mongod.conf

  1. Store data in /usr/local/var/mongodb instead of the default /data/db
    dbpath = /usr/local/var/mongodb
  1. Append logs to /usr/local/var/log/mongodb/mongo.log
    logpath = /usr/local/var/log/mongodb/mongo.log
    logappend = true
  1. Only accept local connections
    bind_ip = 127.0.0.1


 Comments   
Comment by Andrew Morrow (Inactive) [ 27/Feb/17 ]

Thanks for getting back to me and letting me know. I'm closing this ticket.

Comment by Ralph Decatrel [ 27/Feb/17 ]

MongoDB 3.0 does not exhibit this problem, so this issue can be closed.

On Tue, Feb 14, 2017 at 2:55 PM Andrew Morrow (JIRA) <jira@mongodb.org>


Ralph <http://about.me/justronin>
ralph@y12k.com

Comment by Andrew Morrow (Inactive) [ 14/Feb/17 ]

Hi justronin - I just grabbed the latest homebrew mongodb package on a Sierra system, and I do not observe this behavior when starting mongod or the mongo shell. Can you please attempt to reproduce with the latest Sierra updates installed and the latest mongodb homebrew packages? Without a local reproduction I cannot easily verify that the proposed workaround actually fixes anything.

Also, could you please clarify - when you observed these messages, was this a hard stop of the tool or component, or just something logged to the console during startup? If the latter, I'm less inclined to risk a backport to a stable release.

Comment by Ralph Decatrel [ 07/Jan/17 ]

Not yet, need more time

Thanks

Comment by Andrew Morrow (Inactive) [ 07/Jan/17 ]

Hi justronin - Were you able to test any of the newer MongoDB releases to see if they were similarly affected on Sierra?

Comment by Andrew Morrow (Inactive) [ 22/Dec/16 ]

Hi justronin -

Please note that MongoDB 2.6 is end-of-life, and also that at least for me, the mongodb26 homebrew package no longer exists. However, we suspect that this issue exists in later versions of MongoDB as well (well, technically the issue would exist within our built-in copy of gperftools).

Could you please try installing each of the following homebrew mongodb packages on your Seirra machine (unfortunately, I don't currently have access to one or I would do this myself) and see if you still observe this error:

  • mongodb30
  • mongodb32
  • mongodb

The last one is the newly released 3.4. It may be that this issue was resolved already, since we have upgraded the gperftools version across these stable releases. MongoDB 2.6 used gperftools-2.0, MongoDB 3.0 and 3.2 used gperftools-2.2, and MongoDB 3.4 uses gperftools-2.5.

That data would be very valuable to us as it would let us understand which supported stable releases are affected, and help us plan how to manage backporting any fix.

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