Ensure that the Cmd
/Name
/Ref
caches are cleared when terminating the worker (PR 10863 follow-up)
#10873
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Usually when the worker is terminated it will also be completely destroyed/removed, which means that any global caches (such as the ones in
src/core/primitive.js
) should be automatically cleared in the process.However, for certain ways of loading the
pdf.worker.js
file, e.g. passing in a re-usable worker togetDocument
, using theworkerPort
functionality, or even disabling workers completely (even though this is never a good idea), the worker file may be kept in memory and these caches will not be cleared as expected.