Skip to content
This repository was archived by the owner on Sep 9, 2024. It is now read-only.

pointer being freed was not allocated #26

Open
benweet opened this issue Mar 22, 2015 · 6 comments
Open

pointer being freed was not allocated #26

benweet opened this issue Mar 22, 2015 · 6 comments

Comments

@benweet
Copy link

benweet commented Mar 22, 2015

Got this error lately (node 0.10.37, OSX):

node(1166,0x7fff7db64310) malloc: *** error for object 0x1044a9d3d: pointer being freed was not allocated

Getting rid of node-lz4 fixed the problem...
@pierrec
Copy link
Owner

pierrec commented Apr 8, 2015

Looks like an lz4 or node issue. I will update the lz4 source at some point. Do you run into this wih node 0.12.x as well?

@pierrec
Copy link
Owner

pierrec commented Apr 9, 2015

Rebuild with the latest version. It seems to fix the issue.

@benweet
Copy link
Author

benweet commented Apr 9, 2015

Tested with node 0.12. Looks good.

@benweet benweet closed this as completed Apr 9, 2015
@benweet
Copy link
Author

benweet commented Apr 9, 2015

Ooops, no.

node(20465,0x7fff70d24300) malloc: *** error for object 0x10141f100: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

@benweet benweet reopened this Apr 9, 2015
@meash-nrel
Copy link

same malloc bug here

node v0.10.38 on CentOS6

@pierrec
Copy link
Owner

pierrec commented Mar 21, 2016

I havent been able to reproduce this. I have updated the lz4 lib to the lastest C version.
In the meantime, you can still use the pure JS implementation!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pierrec @benweet @meash-nrel