Still broken in Confluence 6.15.1. Deleting the Viewfile plugin cache does not work as a permanent fix.

Atlassian Confluence 6.14.0 : Rendering still broken

Confluence 5.10.4, still present

Confluence 5.6.4, still present

For us, running Confluence 5.5.2, the issue is also still existent. Some PDF pages won't render at all or the Text in PDF documents is broken, with some characters unreadable.

Screenshots:
https://www.evernote.com/shard/s7/sh/11c1643f-97a8-45f9-b3f9-d80cb9592218/be3c3a6cb4cd1127079ba3bc6c216ee8
https://www.evernote.com/shard/s7/sh/8bc3b164-dafe-4e4d-8541-28d0b3eb7bab/8617b71ff1b5cc74bc585e0814a83b2e

fyi: the bug (in reality never resolved) persist in Confluence 5.6.1

Hi burkhard.buelte

Thanks for the update on this and providing the extra information. We suspect that there may be a specific problem on some windows hosted systems that we are currently investigating. I've created the following issue to track this problem: https://jira.atlassian.com/browse/CONF-34096.

Regards
Steve Haffenden
Confluence Bugmaster
Atlassian

Let me stress out again... the viewer bug is not fixed
and pdf files can not be (reliable) viewed in Confluence 5.x.x
(the CONF31759 workaround doesn't change this... deals with other topic)

Let me sum up what I've learned about the bug

• occurs predominant on Windows hosted system
• 1st view of pdf always works
• after time Confluence starts creating *.part files in viewfile directory (in additon to the existing -> from now on some pages of the pdf are not rendered (the bug)
• the viewfile directory and it's temp directory is heavily used under Windows during viewing a pdf
• if you delete the content of the viewfile directory and it's temp, 1st view of pdf always works (so a startover)

And this can not be debuged to it's root cause and fixed by Atlassian ?

If you still experience this issue, you better should vote also for

https://jira.atlassian.com/browse/CONF-32515

Because that's a open bug regarding this issue. Our support representative is trying under CONF-32515 to convince the developers that this bug is worsewhile to be fixed. But CONF-32515 did not yet receive enough votes to get assigned.

Please note that workaround in 5.5.1 solving problems described in https://jira.atlassian.com/browse/CONF-31759 and https://jira.atlassian.com/browse/CONF-31384 - both of them are regression we introduced in version 5.3.

This particular issue (https://jira.atlassian.com/browse/CONF-16922) is a bit more generic and exists starting from confluence 3.0.2.

I'm mentioning this because depends on root cause your problem might or might not be solved by applying workaround.

Btw, would you be able to ask admin to check whenever he sees "WARN [DefaultSlideCacheManager:thread-1] [com.benryan.conversion.MemoryAwarePDFRenderer] drawImage Image of size 2464*3448 px dropped for memory protection" before workaround applied and not seeing it after in log files?