-
Notifications
You must be signed in to change notification settings - Fork 168
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
2 issues: TX.exe crashes on ProofPDF command and additionally a problem with ttf #195
Comments
I have spent many hours to identify the reason for the crash. It seems to be caused by the number of variables I set in a batch script, which is called by all the other batch scripts. There seems to be a limit. But I don't know, why this problem occurs in context with ProofPDF.py and TX. |
The limit of the number of variables, that I can set in the batch file, that is called by the other batch files, that control ProofPDF.py, is round about 65. But it is not the pure number of variables, but the storage space they occupy. I am storing pathes in the variables, but these pathes are not long. So they don't occupy much space. I assume, that ProofPDF.py or TX.exe try to store much data in the same storage place. |
I really doubt that adding more variable int the calling script is a source of the problem. More likely there is an uninitialized variable that is causing crashes depending on whatever happens to be in memory. I will look at this, but it may be a few days before I get there. The second issue looks more like ProofPDF is broken for TTF fonts - fails under Mac OSX for me. |
I know, that it sounds very odd. But I have thoroughly examinated the script. Example: If the script works with 65 variables without the crash of TX in context with the ProofPDF command, but not with 66, it doesn't matter which of the following lines I remove from the script, as long as the lengths of the pathes are similar. All the three Python scripts are present in the path %FDKScripts%. And the AFDKO is stored in the root directory of drive C. (Even if one of the three Python scripts would not be present in %FDKScripts%, it would not matter, because the three variables are not used in the script with the ProofPDF.py command.)
"Fails" means, that you cannot reproduce the issue under Mac OSX? Do you have access to a Windows machine? |
Waterfallplot works with ttf here. |
@readroberts and @anyone with a Windows machine, who wants to try to comprehend / confirm the issue. For an unknown reason Github does not accept my zip file. So I just post a batch script and a readme file as code: Readme.txt
Test_ProofPDF_regarding_to_variables_issue.bat
|
@cjchapman the First issue may be related to the |
The Second issue (ProofPDF fails with TT fonts) got fixed at some point; we have integration tests for all *plot tools and they run fine with TTF inputs. |
#427 seems to have fixed the First issue |
The first of the following issues occurs with the AFDKO, that I have built on 07-06-2017 and on 09-29-2017 (but not with AFDKO 2.5 build 65322).
Python 2.7.11 32 bit / 2.7.14 32 bit
Windows 7
First issue
Example command:
python.exe ProofPDF.py -fontplot -dno -o "Output\Fontplot.pdf" "font.otf"
As you can see, the PDF was generated (after closing the tx crash message popup).
I cannot exclude, that I have made anything wrong, when I had built the AFDKO (because the build notes are not up to date).
Second issue
If the input font is a ttf, ProofPDF totally fails. It also fails with AFDKO 2.5 build 65322, if the input font is a ttf. (That is not related to the TX crash bug.)
The text was updated successfully, but these errors were encountered: