You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I’m not wrong, this fix hasn’t been released yet. Is there an ETA for the next release? No preasure, just want to know if it makes more sense to wait for the update or to downgrade to an older version for now. :-)
Describe the bug
When doing
str(binary)
of a larger binary, it used to work. In >v0.12.3 it ends up in a OOM error.To Reproduce
Steps to reproduce the behavior:
curl -O https://nodejs.org/dist/v20.12.0/node-v20.12.0-linux-arm64.tar.xz tar -xf node-v20.12.0-linux-arm64.tar.xz python -c 'import lief; binary = lief.parse("node-v20.12.0-linux-arm64/bin/node"); print(str(binary))'
Expected behavior
Some stringified value.
Actual behavior
MemoryError: std::bad_alloc
Environment (please complete the following information):
Additional context
Upstream issue: conda/conda-build#5267
Might be similar to #1038?
The text was updated successfully, but these errors were encountered: