StackOverflowError at uri_3a_classloader_3a_.gems.ttfunk_minus_1_dot_7_dot_0.lib.ttfunk.reader.RUBY$method$read_signed$0(uri:classloader:/gems/ttfunk-1.7.0/lib/ttfunk/reader.rb:16) #89
Comments
rocketraman
changed the title
|
It appears as though this error is coming from ttfunk. It likely has to do with either an invalid font or a font which contains something that ttfunk is not anticipating. Either way, if it is an issue with ttfunk, there is little we can do about it in this project. It would need to be reported to ttfunk. Can you tell us whether this happens when using a built-in theme, or only when using a custom theme with your own fonts? |
Given that's the case, it may be that the amount of input is just too large for the amount of memory allocated to the JVM. This is not uncommon when generating PDFs since the process requires a large amount of memory. So we might just have to say that if you see an error like this, it's necessary to allocate more memory to the JVM. (It probably scales linearly with the size of the PDF being generated, and hence the input). |
It is a custom theme with my own fonts. Here is the configuration Here is the calling code:
That's possible. I've only seen the error happen in a memory-constrained container environment. The asciidoc is small (about 6.6k of text) which outputs to about 7 pages. However the logo is 66KB and the font TTFs total about 1.3 MB. The output PDFs are between 160 and 190 KB -- the particular one that failed was 171.6 KB. These containers are at the moment allocated 1Gi of memory. |
|
It could very well be the size of the font, since ttfunk has to go through an process all of the data in it in order to be able to use it. |
I received this
StackOverflowErrorfrom my JVM backend while doing PDF conversions. The error was not specific to the inputs -- the system automatically retried and successfully generated the output for the same inputs.I was not able to reproduce the problem either.
However, hopefully the exception will help with isolating the issue.
The text was updated successfully, but these errors were encountered: