Skip to content
This repository has been archived by the owner on Jan 14, 2025. It is now read-only.

Possible Memory Allocation Error - corrupted size vs. prev_size #198

Open
Daggema opened this issue Nov 9, 2018 · 2 comments
Open

Possible Memory Allocation Error - corrupted size vs. prev_size #198

Daggema opened this issue Nov 9, 2018 · 2 comments

Comments

@Daggema
Copy link

Daggema commented Nov 9, 2018

After running Yabar for a few minutes the process invariably crashes and returns the following error:

corrupted size vs. prev_size
Aborted (core dumped)

After doing some research it seems this error might be indication of a memory allocation issue in the C code:

https://stackoverflow.com/questions/50797993/corrupted-size-vs-prev-size-in-c

Not sure if this is something only I've encountered or if anyone else has had it but seems like it might be worthwhile investigating.

Regards

@tscode
Copy link

tscode commented Nov 21, 2018

I can confirm this issue, running Arch Linux on several different laptops. Sometimes yabar runs for hours, and sometimes it crashes after a few minutes already. I don't see an obvious rule as to when this happens, however.

@gavinstjohn
Copy link

+1 Also having this problem on arch, usually crashed within a couple minutes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants