Description of problem: I was playing with some mapreduce operations that may have triggered an infinite recursion. Version-Release number of selected component: mongodb-server-2.4.6-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: mongod --rest crash_function: StringHasher executable: /usr/bin/mongod kernel: 3.13.10-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 StringHasher at src/objects-inl.h:4900 #1 HashSequentialString<char> at src/objects-inl.h:4979 #2 v8::internal::String::ComputeAndSetHash at src/objects.cc:7226 #3 Hash at src/objects-inl.h:4891 #4 v8::internal::String::SlowAsArrayIndex at src/objects.cc:7279 #5 AsArrayIndex at src/objects-inl.h:4998 #6 v8::internal::Runtime::GetObjectProperty at src/runtime.cc:4003 #7 v8::internal::GetProperty at src/handles.cc:293 #8 v8::Object::Get at src/api.cc:2860 #9 mongo::V8Scope::v8ToMongo at src/mongo/scripting/engine_v8.cpp:1665
Created attachment 891769 [details] File: backtrace
Created attachment 891770 [details] File: cgroup
Created attachment 891771 [details] File: core_backtrace
Created attachment 891772 [details] File: dso_list
Created attachment 891773 [details] File: environ
Created attachment 891774 [details] File: exploitable
Created attachment 891776 [details] File: limits
Created attachment 891777 [details] File: maps
Created attachment 891778 [details] File: open_fds
Created attachment 891779 [details] File: proc_pid_status
Created attachment 891780 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Any reproducer of this bug? Is it still valid for newer mongodb versions?
I don't have access to the test case anymore so I won't be able to check whether the bug is still present or not. You may close this report. Thanks for looking into it though.
OK. I tried it, but the problem is that I wasn't able to reproduce this bug. Feel free to reopen. Thanks...