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.

Sign up for GitHub

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

Jump to bottom

OpenJPEG allocates more memory than stricly needed #275

Open
GoogleCodeExporter opened this issue Jul 18, 2015 · 1 comment
Open

OpenJPEG allocates more memory than stricly needed #275

GoogleCodeExporter opened this issue Jul 18, 2015 · 1 comment
Labels
auto-migrated Priority-Low Type-Defect

Comments

@GoogleCodeExporter
Copy link 

The image structure used to decode a tile uses a 32 bit integer per pixel.
For images with smaller pixel types, this is a waste of memory.

This becomes a problem when decoding several big tiles in parrallel.

Original issue reported on code.google.com by julien.m...@gmail.com on 5 Mar 2014 at 3:55
@GoogleCodeExporter
Copy link
Author 

I am moving this as lower priority. I guess 70% of the symptoms will be gone 
when issue 94 is implemented.

Original comment by mathieu.malaterre on 7 Mar 2014 at 9:11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Low Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter