Issue 1613 in pdfium: FPDF_RenderPage() method takes a long time to render the page

20 views
Skip to first unread message

gdv1… via monorail

unread,
Nov 9, 2020, 12:51:11 PM11/9/20
to pdfiu...@googlegroups.com
Status: Unconfirmed
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1613 by gdv1...@gmail.com: FPDF_RenderPage() method takes a long time to render the page
https://bugs.chromium.org/p/pdfium/issues/detail?id=1613

What steps will reproduce the problem?
Run the following test with the attached PDF:

TEST_F(CPDFParserEmbedderTest, CantRenderPdf) {
auto start = high_resolution_clock::now();

EXPECT_TRUE(EmbedderTest::OpenDocument(
"example_1.pdf"));
FPDF_PAGE page = EmbedderTest::LoadPage(0);
ASSERT_TRUE(page);
ScopedFPDFBitmap page_bitmap = EmbedderTest::RenderPage(page);

auto stop = high_resolution_clock::now();
auto duration = duration_cast<microseconds>(stop - start);
cout << "Time taken by function: " << duration.count() << " microseconds"
<< endl;

WriteBitmapToPng(page_bitmap.get(), "results.png");
}

What is the expected output? What do you see instead?
Expected image with page content, but FPDF_RenderPage() freezes/never returns results.

What version of the product are you using? On what operating system?
PDFium v4103. OS Windows 10.

Please provide any additional information below.
Acrobat Reader can open this PDF

Attachments:
example_1.pdf 522 KB
example_2.pdf 522 KB
example_3.pdf 522 KB

--
You received this message because:
1. The project was configured to send all issue notifications to this address

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

n… via monorail

unread,
Nov 9, 2020, 7:56:37 PM11/9/20
to pdfiu...@googlegroups.com
Updates:
Mergedinto: 1611
Status: Duplicate

Comment #1 on issue 1613 by ni...@chromium.org: FPDF_RenderPage() method takes a long time to render the page
https://bugs.chromium.org/p/pdfium/issues/detail?id=1613#c1

A duplicate bug is filed as crbug.com/pdfium/1611. Will mention this bug has more testing cases in bug 1611.
Reply all
Reply to author
Forward
0 new messages