Jonas Walldén
My feedback
3 results found
-
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment My test case attachment seems to have been lost (I tried to "fix" the filename to get .idml accepted). Please try this link instead:
https://drive.google.com/file/d/10G7qXYWhJKXdf-UGnf4W6HlMlE9NSFqn/view?usp=sharing
An error occurred while saving the comment Sorry for the attachment filename (cc18-infinite-recompose.idml.txt) – the attachment wouldn't be accepted with a plain .idml or .zip extension. Please strip off the .txt extension to get the original IDML file.
An error occurred while saving the comment The attached IDML test case (also applicable to CC15/18 clients) enters an infinite recompose loop directly after opening. The second text column repaints continuously. This in itself doesn't directly block interactive use of the InDesign client since recomposing is a background task, but as soon as one tries to save/export the document to disk the application hangs (most likely waiting for a stable document state).
It's notable that the exact placement of the small text frames containing arrows are a necessary piece of the puzzle. Moving them outside of the main text column stops the recompose loop, but then moving them back to their original position will bring back the problem.
Our use case of opening/processing/saving this document (or rather more complex variants of it) on InDesign Server is therefore entering a state where IDS consumes 100% CPU and never completes the action, thus creating a serious disruption in the workflow.
I have not been able to reproduce the problem with CC19 (I tested 14.0.2.324), but CC15 (11.4.1.102 and .105) as well as CC18 (13.1.0.76) all show the same behavior. I'm using macOS 10.14.3 and our IDS runs on various older macOS installations (10.11.6 is one of them).
I'd be thankful for some input on the following questions:
– Is CC19 fixing this problem by design or am I just lucky to not trigger a similar bug there for now (i.e. the potential risk remains)?
– Any chance of a fix be distributed for CC18 or CC15 in future Rapid Release builds?
– Are there any preconditions in the document that we can change to avoid the buggy code path altogether? E.g. any frame/style/document property that we can instruct our customers to avoid and thereby be safe?
Don't hesitate to ask for more details if needed.
An error occurred while saving the comment The attached IDML test case (also applicable to CC15/18 clients) enters an infinite recompose loop directly after opening. The second text column repaints continuously. This in itself doesn't directly block interactive use of the InDesign client since recomposing is a background task, but as soon as one tries to save/export the document to disk the application hangs (most likely waiting for a stable document state).
It's notable that the exact placement of the small text frames containing arrows are a necessary piece of the puzzle. Moving them outside of the main text column stops the recompose loop, but then moving them back to their original position will bring back the problem.
Our use case of opening/processing/saving this document (or rather more complex variants of it) on InDesign Server is therefore entering a state where IDS consumes 100% CPU and never completes the action, thus creating a serious disruption in the workflow.
I have not been able to reproduce the problem with CC19 (I tested 14.0.2.324), but CC15 (11.4.1.102 and .105) as well as CC18 (13.1.0.76) all show the same behavior. I'm using macOS 10.14.3 and our IDS runs on various older macOS installations (10.11.6 is one of them).
I'd be thankful for some input on the following questions:
– Is CC19 fixing this problem by design or am I just lucky to not trigger a similar bug there for now (i.e. the potential risk remains)?
– Any chance of a fix be distributed for CC18 or CC15 in future Rapid Release builds?
– Are there any preconditions in the document that we can change to avoid the buggy code path altogether? E.g. any frame/style/document property that we can instruct our customers to avoid and thereby be safe?
Don't hesitate to ask for more details if needed.
I can add that this bug can be temporarily mitigated by reverting to the older text shaping engine using the `shapeIndicAndLatinWithHarbuzz` flag, but this is not a long-term fix since it's a global flag and whose availability in future releases is unknown.