Timur Kristóf
Timur Kristóf
I would also appreciate it if you could give me a test case that reproduces this.
@nwbrad Can you please repeat that but using a debug build? So that we can see line numbers in there. The backtrace itself is enough, I can't use the memory...
@nwbrad What I would like to see is line numbers in node-lmdb. For that you don't need the nodejs debuginfo, it is enough to make a debug build of node-lmdb.
> I installed and built nodejs from source But you don't need to. You only need a debug build of **node-lmdb**, not node. ```bash git clone [email protected]:Venemo/node-lmdb.git cd node-lmdb node-gyp...
Thank you @nwbrad the relevant line seems to be `CursorWrap::close (info=...) at ../src/cursor.cpp:94` which tells us that there is a double free somehow in there. Can you give me a...
Not sure what would cause this but I'll investigate. Sorry for the slow reply.
@nwbrad Does it only occur with one specific database, though?
@nwbrad Can you give me some version of this environment (possibly with some dummy data) where I can reproduce this problem?
Thanks @nwbrad I'm looking forward to seeing it.
@nwbrad Any news about this? If you can give me a dataset and some code with which the issue is reproducible I am fairly sure I can fix the problem....