Skip to content

Deep Scanline Input readPixels() and readPixelCounts() crash when using an externally provided framebuffer #2020

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

Open
nikos-foundry opened this issue Apr 11, 2025 · 0 comments · May be fixed by #2019

Comments

@nikos-foundry
Copy link
Contributor

The Deep Scanline Input code has recently been rewritten to make use of the EXR core library. As a result a bug was introduced when using the overloads of readPixels() and readPixelSampleCounts() that use externally provided framebuffers as parameters and a hard crash is occuring. According to the comment on the header of these functions, when these overloads are used the InputFile's frameBuffer is not used.

However both these functions call into readMemData(), which does use the InputFile's member framebuffer, which has not been allocated, resulting into a segmentation fault.

I have raised a pull request that I believe fixes this issue: #2019

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

Successfully merging a pull request may close this issue.

1 participant