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

[api-minor] Fetch binary CMap data in the worker-thread, when useWorkerFetch is set #13514

Merged
merged 2 commits into from
Jun 8, 2021

Conversation

Snuffleupagus
Copy link
Collaborator

This patch uses the new option added in PR #12726 to also allow fetching binary CMap data directly in the worker-thread in browsers.
Given that these changes remove the need to transfer data between threads for the default (browser) use-case, we can also revert the changes in PR #11118 since that simplifies the overall implementation.

@Snuffleupagus Snuffleupagus changed the title Fetch binary CMap data in the worker-thread, when useWorkerFetch is set [api-minor] Fetch binary CMap data in the worker-thread, when useWorkerFetch is set Jun 8, 2021
Copy link
Contributor

@brendandahl brendandahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

r+ with fix below

src/core/evaluator.js Outdated Show resolved Hide resolved
…ontDataFactory` to their own file

Given that these factories are being used in *different* files, for Browser respectively Node.js implementations, it seems reasonable to move them into their own file instead.
… set

This patch uses the new option added in PR 12726 to *also* allow fetching binary CMap data directly in the worker-thread in browsers.
Given that these changes remove the need to transfer data between threads for the default (browser) use-case, we can also revert the changes in PR 11118 since that simplifies the overall implementation.
@pdfjsbot
Copy link

pdfjsbot commented Jun 8, 2021

From: Bot.io (Linux m4)


Received

Command cmd_test from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.67.70.0:8877/eba10bff5bb4366/output.txt

@pdfjsbot
Copy link

pdfjsbot commented Jun 8, 2021

From: Bot.io (Windows)


Received

Command cmd_test from @Snuffleupagus received. Current queue size: 0

Live output at: http://3.101.106.178:8877/65113f94ea0bd7f/output.txt

@mozilla mozilla deleted a comment from pdfjsbot Jun 8, 2021
@mozilla mozilla deleted a comment from pdfjsbot Jun 8, 2021
@mozilla mozilla deleted a comment from pdfjsbot Jun 8, 2021
@mozilla mozilla deleted a comment from pdfjsbot Jun 8, 2021
@pdfjsbot
Copy link

pdfjsbot commented Jun 8, 2021

From: Bot.io (Linux m4)


Failed

Full output at http://54.67.70.0:8877/eba10bff5bb4366/output.txt

Total script time: 26.17 mins

  • Font tests: Passed
  • Unit tests: Passed
  • Integration Tests: Passed
  • Regression tests: FAILED

Image differences available at: http://54.67.70.0:8877/eba10bff5bb4366/reftest-analyzer.html#web=eq.log

@pdfjsbot
Copy link

pdfjsbot commented Jun 8, 2021

From: Bot.io (Windows)


Failed

Full output at http://3.101.106.178:8877/65113f94ea0bd7f/output.txt

Total script time: 29.85 mins

  • Font tests: Passed
  • Unit tests: Passed
  • Integration Tests: FAILED
  • Regression tests: FAILED

Image differences available at: http://3.101.106.178:8877/65113f94ea0bd7f/reftest-analyzer.html#web=eq.log

@Snuffleupagus Snuffleupagus merged commit ae531e5 into mozilla:master Jun 8, 2021
@Snuffleupagus Snuffleupagus deleted the base_factory branch June 8, 2021 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants