We’ve just fixed the issue in the development build.
The reason is that in the problematic PDF an image size is unexpectedly given not as an integer, but as a reference to another object (which holds only an integer). Now the case is correctly worked around.
Viewing 2 posts - 1 through 2 (of 2 total)
The forum ‘Troubleshooting’ is closed to new topics and replies.