-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
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
inserting a bunch of std::strings #62
Comments
@roblatham00 Looks like the GC has problem with freeing memory properly (or failed to initialize, imo). I will take a look into this issue. |
Discussions on our end were wondering if I made a mistake by declaring the string inside the while loop. What does BwTree expect from the caller with respect to scope and lifetimes? |
@roblatham00 The bug is not related to the scope of the string, but rather has something to do with the destructor. I have narrowed down the cause of the bug, and it seems to me that this happens at the first GC cycle, during the destructor call of a leaf base node. I was traveling outside of the US recently and may not be able to response very quickly. My apology here. I will notify you once I resolve the GC problem. BTW, the design goal is to fully support C++ object semantics, but there are implementation issues with that (e.g. BwTree moves Key/Value objects frequently compared with other indices, and therefore the usage of non-POD types as keys or values might suffer from performance loss). |
We are bumping into this issue now that we are scaling up a bit. Any progress on this bug? Anything we can do to help debug? thanks. |
I am probably doing something wrong here, but when I try to add a bunch of strongs to the BwTree I get a segfault. It behaves as expected with integers. Please forgive the C-like use of your class -- I'm much more of a C programmer than a C++ programmer.
It runs for a few iterations then eventually stops:
The core file is hairy, but I can post the full thing if you think it will be helpful. here are the first few frames:
The text was updated successfully, but these errors were encountered: