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

Fix #2596 #2711

Merged
merged 3 commits into from
Oct 5, 2023
Merged

Fix #2596 #2711

merged 3 commits into from
Oct 5, 2023

Conversation

JorjMcKie
Copy link
Collaborator

When continuing to use a page object after the PDF has been saved with garbage options may change the MuPDF cache such that e.g. rendering the page after the save will produce wrong appearance or even garbled appearance. The user needs to reload the page (page = doc.reload(page)) before using it further, especially for rendering. The reload method now always empties the cache.

When continuing to use a page object after the PDF has been saved with garbage options may change the MuPDF cache such that e.g. rendering the page after the save will produce wrong appearance or even garbled appearance.
The user needs to reload the page (page = doc.reload(page)) before using it further, especially for rendering.
The reload method now always empties the cache.
JorjMcKie and others added 2 commits October 3, 2023 12:41
The underlying fz_page was being kept alive so reload_page()'s call of
fz_load_page() was returning it from the document's internal list of pages
instead of regenerating it.
@JorjMcKie
Copy link
Collaborator Author

Thanks!

@JorjMcKie JorjMcKie merged commit 7658e42 into main Oct 5, 2023
2 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Oct 5, 2023
@JorjMcKie JorjMcKie deleted the fix-2596 branch October 5, 2023 12:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants