-
Notifications
You must be signed in to change notification settings - Fork 45
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
InvalidMemoryOperation on mongo queries #107
Comments
Usually setting a breakpoint at |
I don't have that symbol... I'm building with the latest dmd on linux. Do I need any special setup?
|
Ah, sorry, that should be |
awesome! thanks... I have a stack now. I'll try to give some time to this issue.
|
@s-ludwig I managed to trace down this issue. It looks like the this is a vibe-core function allocates here: https://github.com/vibe-d/vibe-core/blob/master/source/vibe/core/connectionpool.d#L92 is there a reason why this MongoCursor.destroy operation needs a new connection? |
This got kind of lost here in the vibe-core repository, but what looks like is happening here is that the cursor hasn't been fully processed, so a But I will add an assertion to provide a better error message/location. |
Actually, reviewing the code, I have already "fixed" this in vibe-d/vibe.d#2794 (fix for pretty much the same issue, vibe-d/vibe.d#2793) - it now simply logs an error. Making this a hard error is IMO the better approach, but I will leave it like this for now. |
I get the following error almost every time when I start m app. I tried to reduce the code to a small example, but I cound not find the main problem:
The text was updated successfully, but these errors were encountered: