Skip to content
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

Allocator error in bug-42-sample015.ogg #43

Open
est31 opened this issue Feb 26, 2019 · 3 comments
Open

Allocator error in bug-42-sample015.ogg #43

est31 opened this issue Feb 26, 2019 · 3 comments
Labels

Comments

@est31
Copy link
Member

est31 commented Feb 26, 2019

Issue #42 was about a panic in residue_packet_read_partition but after fixing it, one of the samples now triggers a second allocator based error.

You'd get an error like:

fatal runtime error: allocator memory exhausted

And then a segfault.

@est31 est31 added the bug label Feb 26, 2019
@est31
Copy link
Member Author

est31 commented Feb 26, 2019

Nice, even gdb segfaults when I'm trying to study the error.

@est31
Copy link
Member Author

est31 commented Feb 26, 2019

Hmm, with Rust stable there is no gdb segfault.

Backtrace points to the error originating in lewton::header::read_header_comment (packet=...) at src/header.rs:329.

Yeah it seems it wants 1979711488 many comments. Quite a number!

@Shnatsel
Copy link
Contributor

Oh, I have a whole bunch of OOM-crashing samples from fuzzer. Here you go: oom-samples.zip

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

No branches or pull requests

2 participants