randy.willeyefi.com Posted October 24, 2013 Posted October 24, 2013 Are there any known support issues using FusionPro 9.0.3 on a Mac OS X Mavericks OS? Quote
Alex Marshall Posted October 24, 2013 Posted October 24, 2013 Apple Macintosh OSX 10.9 Maverick is not currently supported with Fusionpro as it is currently in the development stages at this time. We will notify our customers as soon as a release candidate becomes available. We appreciate your patience with this matter. Quote
juliazo Posted October 24, 2013 Posted October 24, 2013 Since Mavericks was officially released, I went ahead and upgraded one of our workstations to test out how FusionPro behaves with it. And it doesn't do very well: seems like Fonts (new/all) cannot be loaded, causing the plugin to crash. Quote
Alex Marshall Posted October 24, 2013 Posted October 24, 2013 Sorry for the trouble you are encountering with the software. The second issue you encountered, specifically on your OSX system is a result of Fusionpro encountering corrupt fonts. The following solution should resolve this issue. Your system needs the font Cache cleaned due to bad fonts. The following should help. Please perform the detailed steps to resolve this problem. The solution is to do the following. Locate the "FusionPro Configuration" file in "/Library/Application Support/PTI/FusionPro", open it in TextEdit (or another editor), and add this line at the end: LogAllLoadedFonts=Yes Then save the file, and go back to FusionPro and load all fonts. Fusionpro Load Fonts utility will crash on a font with the message, "Fusionpro quit unexpectedly". Now, navigate the hard drive to: Mac HD / Library / Preferences / PTI / Fusionpro / Fonts In this folder, locate the 'Fonts.err" file and open with Text Editor. Look at the very last line in this log file. It will indicate the last font that cause it to crash. Delete or remove this font completely from the system. Rerun "Load Fonts" "Load All" You will repeat these steps until the Load Fonts utility completes without crashing. Once completed, restart the machine and rerun Fusionpro to see if this helps. You can also utilize third party font software to isolate corrupt fonts on the Mac OSX. Quote
juliazo Posted October 24, 2013 Posted October 24, 2013 Thank you, Alex!! The issue, however, persists, as the last font in the font.err log is AvenirNext, a system font that I can't disable or uninstall I'm trying FontNuke to flush my font caches and whatnot, will report back shortly. Quote
Dan Korn Posted October 24, 2013 Posted October 24, 2013 Since Mavericks was officially released, I went ahead and upgraded one of our workstations to test out how FusionPro behaves with it. And it doesn't do very well: seems like Fonts (new/all) cannot be loaded, causing the plugin to crash. From which previous version of OS X did you update? Also, what is the version of FusionPro? Quote
juliazo Posted October 24, 2013 Posted October 24, 2013 (edited) Hi Dan, Updated from 10.8.4 to 10.9 on a month-old MacBook Pro (Retina, 15-inch, Mid 2012). Fusion Pro v9.0.3, Adobe CS 6 (Acrobat v10.1.8). As an update, after trying FontNuke, FusionPro is still crashing. Edited October 24, 2013 by juliazo Quote
Dan Korn Posted October 24, 2013 Posted October 24, 2013 Updated from 10.8.4 to 10.9 on a month-old MacBook Pro (Retina, 15-inch, Mid 2012). Fusion Pro v9.0.3, Adobe CS 6 (Acrobat v10.1.8). As an update, after trying FontNuke, FusionPro is still crashing. Thanks for the info. As Alex said, we don't officially support Mavericks. But this information will help us to find and fix Mavericks-specific issues. To clarify: Before you said that loading fonts was "causing the plugin to crash." Is it Acrobat that's crashing, or the FusionPro app, or both? What happens if you load fonts just from the FusionPro app, without Acrobat running? Quote
juliazo Posted October 24, 2013 Posted October 24, 2013 (edited) To clarify: Before you said that loading fonts was "causing the plugin to crash." Is it Acrobat that's crashing, or the FusionPro app, or both? What happens if you load fonts just from the FusionPro app, without Acrobat running? It's just the FusionPro app/plugin, and it happens also if I load fonts from the FusionPro app separately from Acrobat. Also, when I open a template, I get that error message that fonts are not loaded, and if I go to FusionPro > Advanced > Font Usage to try and replace fonts, the drop-down that shows available fonts is empty (the drop-down cannot even be clicked on). Edited October 25, 2013 by juliazo typos Quote
juliazo Posted November 1, 2013 Posted November 1, 2013 Hi guys, An update on this issue: I wiped and reinstalled the OS on my MacBook Pro (Retina, 15-inch, Early 2013). With nothing but OS X 10.9 installed, I installed Adobe CS6 Standard, then FusionPro 9.1.0. During the initial font search (the one that happens at the end of the installation), the FusionPro app crashed. Below is the crash report, which seems to point at an issue with the font Avenir Next. Tried to disable it, but no go, it's a system font so I'm not allowed to do so. Any advice welcome and appreciated. Crash report: Process: FusionPro [11743] Path: /Applications/PTI/*/FusionPro.app/Contents/MacOS/FusionPro Identifier: com.pti.fusionpro.server Version: 9.1.0 (9.1.0) Code Type: X86 (Native) Parent Process: launchd [385] Responsible: FusionPro [11743] User ID: 501 Date/Time: 2013-11-01 14:44:52.073 -0700 OS Version: Mac OS X 10.9 (13A603) Report Version: 11 Anonymous UUID: C034851E-80BE-A571-7D56-24E1026B3E9C Sleep/Wake UUID: DE1F45AF-0D69-4460-9D94-9E0EECDA6857 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000249aa038 VM Regions Near 0x249aa038: mapped file 0000000012d85000-0000000013278000 [ 5068K] rw-/rwx SM=COW /System/Library/Fonts/Avenir Next.ttc --> __TEXT 0000000033000000-00000000330be000 [ 760K] r-x/rwx SM=COW /Applications/PTI/*/FusionPro.app/Contents/Frameworks/JS.framework/Versions/A/JS Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.pti.fusionpro.server 0x00536fcd AddKernEntries(std::vector<CDTLKern, std::allocator<CDTLKern> >&, unsigned short, unsigned short, short, std::vector<RevMapEntry, std::allocator<RevMapEntry> > const&, unsigned short*) + 381 1 com.pti.fusionpro.server 0x005a3527 GetKern0Entries(unsigned long, kern_entry0*, head_table const&, std::vector<RevMapEntry, std::allocator<RevMapEntry> > const&, CDTLFont&) + 341 2 com.pti.fusionpro.server 0x005a5b08 GetTTKerning(unsigned long, head_table const&, std::vector<RevMapEntry, std::allocator<RevMapEntry> > const&, CDTLFont&) + 818 3 com.pti.fusionpro.server 0x005a8ed0 GetMacintoshFonts(__sFILE*, int) + 3628 4 com.pti.fusionpro.server 0x004af328 PostScriptFontLoader::LoadFonts(__sFILE*) + 294 5 com.pti.fusionpro.server 0x003b090e ConvertPFMFontToBFK + 194 6 com.pti.fusionpro.server 0x003da798 LoadFontFromInstall + 112 7 com.pti.fusionpro.server 0x00045cfe CMacGUIServer::DoReloadFonts(int, bool) + 30 8 com.pti.fusionpro.server 0x0004693c CMacGUIServer::HandleAppleEvent(AEDesc const&, AEDesc&, AEDesc&, long) + 236 9 com.pti.fusionpro.server 0x00837be5 LModelObject::HandleAppleEventAll(AEDesc const&, AEDesc&, AEDesc&, long) + 335 10 com.pti.fusionpro.server 0x00836174 LModelDirector::HandleAppleEvent(AEDesc const&, AEDesc&, long) + 244 11 com.pti.fusionpro.server 0x0083636c LModelDirector::AppleEventHandler(AEDesc const*, AEDesc*, long) + 80 12 com.apple.AE 0x95a89b15 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 387 13 com.apple.AE 0x95a58ed6 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44 14 com.apple.AE 0x95a58dce aeProcessAppleEvent + 318 15 com.apple.HIToolbox 0x944f97c1 AEProcessAppleEvent + 55 16 com.pti.fusionpro.server 0x00844acd LEventDispatcher::EventHighLevel(EventRecord const&) + 29 17 com.pti.fusionpro.server 0x008443b3 LEventDispatcher::DispatchEvent(EventRecord const&) + 493 18 com.pti.fusionpro.server 0x008408b8 LApplication::ProcessNextEvent() + 212 19 com.pti.fusionpro.server 0x00048152 CMacGUIServer::ProcessNextEvent() + 18 20 com.pti.fusionpro.server 0x00840618 LApplication::Run() + 162 21 com.pti.fusionpro.server 0x00045c06 main + 760 22 com.pti.fusionpro.server 0x00044d72 _start + 216 23 com.pti.fusionpro.server 0x00044c99 start + 41 Thread 1: 0 libsystem_kernel.dylib 0x9597e046 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x9594edcf _pthread_wqthread + 372 2 libsystem_pthread.dylib 0x95952cce start_wqthread + 30 Thread 2:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x9597e992 kevent64 + 10 1 libdispatch.dylib 0x929728bd _dispatch_mgr_invoke + 238 2 libdispatch.dylib 0x92972556 _dispatch_mgr_thread + 52 Thread 3: 0 libsystem_kernel.dylib 0x9597e046 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x9594edcf _pthread_wqthread + 372 2 libsystem_pthread.dylib 0x95952cce start_wqthread + 30 Thread 4: 0 libsystem_kernel.dylib 0x9597e046 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x9594edcf _pthread_wqthread + 372 2 libsystem_pthread.dylib 0x95952cce start_wqthread + 30 Thread 5: 0 libsystem_kernel.dylib 0x9597e046 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x9594edcf _pthread_wqthread + 372 2 libsystem_pthread.dylib 0x95952cce start_wqthread + 30 Thread 6: 0 libsystem_kernel.dylib 0x9597e046 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x9594edcf _pthread_wqthread + 372 2 libsystem_pthread.dylib 0x95952cce start_wqthread + 30 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x249aa038 ebx: 0x005a80b5 ecx: 0x000002e7 edx: 0x249aa038 edi: 0x000002e7 esi: 0x04246a40 ebp: 0xbfffe7d8 esp: 0xbfffe770 ss: 0x00000023 efl: 0x00010286 eip: 0x00536fcd cs: 0x0000001b ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f cr2: 0x249aa038 Logical CPU: 0 Error Code: 0x00000004 Trap Number: 14 --Shortened due to posting limitations-- Quote
juliazo Posted November 1, 2013 Posted November 1, 2013 Another update: Deleted the offending font file manually, the program still crashes, the error is now different (no reference to a font, but rather seems to point to Mavericks' memory virtualization technology?): Crash Report Process: FusionPro [291] Path: /Applications/PTI/*/FusionPro.app/Contents/MacOS/FusionPro Identifier: com.pti.fusionpro.server Version: 9.1.0 (9.1.0) Code Type: X86 (Native) Parent Process: launchd [155] Responsible: FusionPro [291] User ID: 501 Date/Time: 2013-11-01 15:21:28.033 -0700 OS Version: Mac OS X 10.9 (13A603) Report Version: 11 Anonymous UUID: C034851E-80BE-A571-7D56-24E1026B3E9C Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c4a463f8 VM Regions Near 0xc4a463f8: CG shared images 00000000c4672000-00000000c467a000 [ 32K] r--/r-- SM=SHM --> Submap 00000000ffff0000-00000000ffff1000 [ 4K] r--/r-- SM=PRV process-only VM submap Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.pti.fusionpro.server 0x00536fcd AddKernEntries(std::vector<CDTLKern, std::allocator<CDTLKern> >&, unsigned short, unsigned short, short, std::vector<RevMapEntry, std::allocator<RevMapEntry> > const&, unsigned short*) + 381 1 com.pti.fusionpro.server 0x005a3527 GetKern0Entries(unsigned long, kern_entry0*, head_table const&, std::vector<RevMapEntry, std::allocator<RevMapEntry> > const&, CDTLFont&) + 341 2 com.pti.fusionpro.server 0x005a5b08 GetTTKerning(unsigned long, head_table const&, std::vector<RevMapEntry, std::allocator<RevMapEntry> > const&, CDTLFont&) + 818 3 com.pti.fusionpro.server 0x005a8ed0 GetMacintoshFonts(__sFILE*, int) + 3628 4 com.pti.fusionpro.server 0x004af328 PostScriptFontLoader::LoadFonts(__sFILE*) + 294 5 com.pti.fusionpro.server 0x003b090e ConvertPFMFontToBFK + 194 6 com.pti.fusionpro.server 0x003da798 LoadFontFromInstall + 112 7 com.pti.fusionpro.server 0x00045cfe CMacGUIServer::DoReloadFonts(int, bool) + 30 8 com.pti.fusionpro.server 0x00045e4c CMacGUIServer::ObeyCommand(long, void*) + 226 9 com.pti.fusionpro.server 0x0084158a LCommander::ProcessCommand(long, void*) + 108 10 com.pti.fusionpro.server 0x008447a0 LEventDispatcher::ClickMenuBar(EventRecord const&) + 136 11 com.pti.fusionpro.server 0x00844601 LEventDispatcher::EventMouseDown(EventRecord const&) + 153 12 com.pti.fusionpro.server 0x008442ae LEventDispatcher::DispatchEvent(EventRecord const&) + 232 13 com.pti.fusionpro.server 0x008408b8 LApplication::ProcessNextEvent() + 212 14 com.pti.fusionpro.server 0x00048152 CMacGUIServer::ProcessNextEvent() + 18 15 com.pti.fusionpro.server 0x00840618 LApplication::Run() + 162 16 com.pti.fusionpro.server 0x00045c06 main + 760 17 com.pti.fusionpro.server 0x00044d72 _start + 216 18 com.pti.fusionpro.server 0x00044c99 start + 41 Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x9597e992 kevent64 + 10 1 libdispatch.dylib 0x929728bd _dispatch_mgr_invoke + 238 2 libdispatch.dylib 0x92972556 _dispatch_mgr_thread + 52 Quote
buggy Posted November 15, 2013 Posted November 15, 2013 (edited) Hi Guys, I'm experiencing this exact same issue... FusionPro crashing on Avenir Next Regular... INFO: Using font name "Avenir Next Regular" instead of family name "Avenir Next". ** LogAllLoadedFonts: Located font: AvenirNext-BoldItalic When opening a template, no fonts are selectable. It's like there are no fonts being loaded to FusionPro. I ran on Mavericks for a week or so with no problem until I had to load fonts and this broke FusionPro's access to all fonts. Same thing. Running Mavericks with Fusion Pro 9.1.0/Acrobat XI Pro on MacBook Pro 17-inch, Mid 2010 8GB RAM 2.8 GHz Intel Core i7 Edited November 15, 2013 by buggy Quote
rofferten Posted November 19, 2013 Posted November 19, 2013 Hi all. I´m having the same crash. FP app crashes, while Acrobat is still running. After deleting "Avenir Next.tcc" and "Avenir Next Condensed.tcc" from "Macintosh HD/System/Library/Fonts", the problem goes away. Not sure what else goes wrong when these system fonts are missing. Acrobat X (10.1.8), Mavericks, FP 9.1.0. Quote
Alex Marshall Posted November 19, 2013 Posted November 19, 2013 Unfortunately, you will continue to have these issues as OSX 10.9 Maverick is not supported in Fusionpro at this time. A build is currently in the development stages at this time. We will notify our customers as soon as a release candidate becomes available. Thank you for your patience. Quote
dalespivey Posted November 20, 2013 Posted November 20, 2013 Out of curiosity, is PTI a member of Apple's ADC? Quote
Dan Korn Posted November 25, 2013 Posted November 25, 2013 Out of curiosity, is PTI a member of Apple's ADC? I'm not sure how knowing the answer to that would help you, but yes, we are. Quote
dalespivey Posted November 26, 2013 Posted November 26, 2013 Thanks, Dan. I haven't been involved with Apple's ADC in years, they used to be very helpful with getting OS upgrade adjustments made. I've been running dual machines one with 10.8 and the other with 10.9. I'm not running into any troubles with Mavericks but I also noticed that I don't have Avenir loaded either. Best of luck. Quote
Dan Korn Posted November 26, 2013 Posted November 26, 2013 Thanks, Dan. I haven't been involved with Apple's ADC in years, they used to be very helpful with getting OS upgrade adjustments made. They may be helpful in terms of fixing reported issues in beta builds of new versions of OS X, but let's just say they're not so helpful in terms of helping you to port your code constantly to support new operating system APIs and architectures. Quote
Hadrian Posted January 2, 2014 Posted January 2, 2014 Any news or timetable on when VDP Creator will be updated to run on Mavericks? Quote
Dan Korn Posted January 9, 2014 Posted January 9, 2014 Any news or timetable on when VDP Creator will be updated to run on Mavericks? I'm actually working on this right now. Unfortunately, I can't give you a release date, but we hope to have a fix in a new release, either 9.1 or 9.2, sometime this quarter, perhaps next month. Thanks to all for your continued patience, and for the crash reports. We have identified two main issues with Mavericks. One issue is related to product registration, and the other is related to fonts with multiple kerning sub-tables (which is the cause of the crash that juliazo reported). Both of these issues prevent new installations of FusionPro on Mavericks, but if you already have FusionPro installed under an older version of OS X, and then upgrade to Mavericks, most things will probably work, as long as you don't try to re-install or re-load fonts. But this configuration is still not supported. Quote
ADRTLister Posted February 13, 2014 Posted February 13, 2014 Glad to know you guys are working on this! Came up for me today when, for the first time, our client decided to switch the font they use for their mailing information. Please keep us all updated on patches as soon as possible, I'll try to find workarounds to keep them happy until then. Quote
juliazo Posted March 7, 2014 Posted March 7, 2014 (edited) Hi guys, Any news/updates on Mavericks support? Also, wasn't able to find the answer to this in the documentation or in the website, so I'll ask here: is VDP Creator 9.1 compatible with Adobe CC? Thanks! Edited March 7, 2014 by juliazo Edited for clarity Quote
Dan Korn Posted March 7, 2014 Posted March 7, 2014 Any news/updates on Mavericks support? We're working very hard on this right now. I can't guarantee anything, but we expect to have FusionPro VDP 9.2, and FusionPro Expression 3.2, both with (almost) full support for Mavericks, out by the end of this month. If you contact Support, they may be able to provide you with a Beta which runs under Mavericks with some caveats. Also, wasn't able to find the answer to this in the documentation or in the website, so I'll ask here: is VDP Creator 9.1 compatible with Adobe CC? Thanks! No. We expect to support InDesign CC later this year. It's our understanding that all users of InDesign CC have access to InDesign CS6, which we do support in FusionPro 9. Quote
-Lisa- Posted March 12, 2014 Posted March 12, 2014 Following up on the Maverick error: Is Maverick OS supported with Fusion Pro yet? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.