We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please use this template for reporting suspected bugs or requests for help.
I have built OpenR and tested it in a mininet env. But the log on each instance shows the following error:
E0708 02:45:17.745582 266847 Util.cpp:190] Failed to read thread allocated/de-allocated bytes: mallctl: not using jemalloc
It seems that the error is not fatal to break OpenR, is it an incorrect invoke of folly?
Code in Util.cpp that throws the error:
uint64_t getThreadBytesImpl(bool isAllocated) { uint64_t bytes{0}; const char* cmd = isAllocated ? "thread.allocated" : "thread.deallocated"; try { folly::mallctlRead(cmd, &bytes); } catch (const std::exception& ex) { XLOG(ERR) << "Failed to read thread allocated/de-allocated bytes: " << ex.what(); } return bytes; }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please use this template for reporting suspected bugs or requests for help.
Issue Description
I have built OpenR and tested it in a mininet env. But the log on each instance shows the following error:
Environment
It seems that the error is not fatal to break OpenR, is it an incorrect invoke of folly?
Code in Util.cpp that throws the error:
The text was updated successfully, but these errors were encountered: