Not for me. Interactive containers are crashing pretty frequently/consistently in both 13.0v5 and 14.0v1 on my Yosemite Mac.
Thats encouraging to hear. My clients haven't updated to FM14 yet... my concern however, is that I have witnessed similar crashes when dragging pdf into container fields (or even viewing them) even without adobe internet plug-ins installed... so I wonder if there are other circumstances that may remain unresolved.
I just also tested 10.10.3 and noticed the same difference between 13 and 14 on it. The latter didn't crash.
Maybe our original issues are different ones ? I can replicate crash with the same file on v13 where steps are Insert a PDF or viewing existing PDF when browsing records, and only when the Adobe reader is activated as an Internet plug-in.
After minutes and several attempts of playing with the same files, v14 never crashed whether it took less than 30 seconds with v13.
Maybe my tests are not valid since 64 bit version exploit better a lot of RAM (i have 12 Gb and more) and yours is lower ?
Also did you get 11.0.11 Adobe version ?
stephensexton a écrit:
[…] even without adobe internet plug-ins installed... so I wonder if there are other circumstances that may remain unresolved.
What i can tell is that "mine" is clearly a different issue since it never occurred when i used Apple preview to display the Interactive Container -- that was the only known workaround.
I am not sure to remember i think it occurred especially when certain common type of images were embedded on the PDF file (jpg or png) which is very very usual.
I have had nothing but issues with interactive containers so I just do not use them at all. I consider it a useless feature of the product.
I unfortunately does not understand you comment because my english is poor, but :
if you have not any use of IC, why would you notice any issue with them ?
I used them in the past and had problems. I do not use them anymore.
The IC dependance of Internet plugins installed on client's computer is for sure a variable that you unfortunately cannot manage from the developer point of vue.
It is more TS related.
I just retrieved a TS update about this issue in the public forum, when cleaning up my mailbox …
Thus, you can also get more info about the bug i was referring to.