tracker issue : CF-4198388

select a category, or use search below
(searches all categories and all time range)

Font disappears after some uptime

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/CannotReproduce

Reporter/Name(from Bugbase): e-domizil License Team / e-domizil License Team ()

Created: 03/06/2017

Components: Document Management, PDF generation

Versions: 2016

Failure Type: Data Corruption

Found In Build/Fixed In Build: CF10 all updaters & CF2016 all updaters (Currently Updater 3 is released) /

Priority/Frequency: Normal / All users will encounter

Locale/System: / Win 2012 Server x64

Vote Count: 0

Problem Description: We are running lots of CFDOCUMENT to generate PDF. After some time CFDOCUMENT creates PDFs that are no longer using "Verdana" font. They fall back to "Verdana Bold" as Verdana seems missing. We verified with getAllFonts() that the Verdana font is no longer there. After restarting the CF instance the font is back and works normally.

This issue exists for an extended time. We have also seen it in CF10 and now it still exists in CF2016. It happens very intermittent.

Steps to Reproduce:

<cfset environ = createObject("java", "java.awt.GraphicsEnvironment").getLocalGraphicsEnvironment()>
<cfset allFamilies = environ.getAllFonts()>
<cfloop from="1" to="#ArrayLen(allFamilies)#" index="i">
#i#: #allFamilies[i].getFamily()# #allFamilies[i].getFontName()#<br/>

Actual Result: Broken PDFs generated.

Expected Result: No broken PDFs

Any Workarounds: Restart CF service



Comment by Alexander H.
1133 | March 06, 2017 10:21:38 AM GMT
Hi, Do you have a test case where you actually generate the PDF's? That would be very useful if you can provide one. Also, is there any approximate number of calls you amke after which the issue starts reproducing? Thanks, Kailash
Comment by Kailash B.
1134 | March 10, 2017 09:33:26 AM GMT
I think there is no specific PDF generation that is causing this. It is highly intermittend and we have no clue how to reproduce. If it would be the bug of java it need to be reproducible. With the knownledge of the bug and your java code, can you create a repro case we can run on our system to verify if this is really the root cause? It could be something totally different...
Comment by Alexander H.
1135 | September 07, 2017 03:07:04 PM GMT
Hi, I tried various scenarios to try and repro this issue in 3 different machines and am unable to do it. We will definitely need a proper test case/usage scenario where this fails. Thanks, Kailash
Comment by Kailash B.
1136 | September 27, 2017 06:10:37 AM GMT
We will reopen if the customer comes back with a test case where its failing
Comment by Kailash B.
29561 | August 21, 2018 06:06:04 AM GMT