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

JVM Crash with SIGSEGV still possible when calling WebP-methods directly #7

Open
pbi-qfs opened this issue Sep 2, 2020 · 0 comments
Open

JVM Crash with SIGSEGV still possible when calling WebP-methods directly #7

pbi-qfs opened this issue Sep 2, 2020 · 0 comments

Comments

@pbi-qfs
Copy link

pbi-qfs commented Sep 2, 2020 •
edited
Loading

#1 fixes the SIGSEGV for the case when WebPWriter is used, only. Since WebP.encodeRGBA, WebP.encodeRGB(and btw. WebP.decode) are public API, the crash can still happen when the methods are called, which forward the object to JNI only by the .fPointer.
pbi-qfs added a commit to pbi-qfs/webp-imageio that referenced this issue Sep 2, 2020
@pbi-qfs
close sejda-pdf#7: Prevent garbage collection of Encoder/Decoder obje…
db476cc 
…cts during native encode/decode calls
@gotson gotson mentioned this issue Oct 14, 2020
Open
joostoudeman pushed a commit to joostoudeman/webp-imageio that referenced this issue Jun 16, 2023
@mateuszkwiecinski
Merge pull request sejda-pdf#7 from usefulness/updates
9190fca 
Add MacOS ARM support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pbi-qfs