Forum Replies Created
-
AuthorPosts
-
October 31, 2014 at 11:24 am in reply to: InDesign CC 2014 October Release Crashes (OS X 10.9.5) #71360
Caleb Clauset
ParticipantAndrew, you aren’t alone. We were surprised to find that, contrary to assurances from Adobe, that plugins for InDesign CC 2014 may not be fully compatible with InDesign CC 2014.1. In all likelihood you are in a similar situation where a _third-party plug-in_ is causing the crash.
As a third-party developer, we’re in a unique situation where we can either recompile using the 2014.1 SDK (which shouldn’t be required but fixes the crash) but lose compatibility with 2014 (10.0) users, or we use the original 2014 SDK (which should be compatible with 2014.1, but apparently isn’t) but crash InDesign CC 2014.1. Obviously we’re choosing the former of recompiling our plug-ins using the 2014.1 SDK and encouraging customers to update to the October release (if they haven’t already). We’re also working with Adobe to identify what changed in the release build (x71) as our plug-ins were working fine during pre-release testing (up to build x70).
As far as re-installing the June release, it’s definitely possible but you cannot have both the June (10.0) and October (10.1) releases simultaneously installed. Do the following:
# Launch the Adobe Creative Cloud desktop application.
# Go to the Apps tab
# Scroll down past your _Installed Apps_ to the _Find New Apps_ section.
# To the right of the section heading, you’ll see a text ‘button’ labelled _Filters & Versions_; click that and then choose _Previous Version_
# Now when you click on the InDesign _Install_ button you should see options for CS6 8.0, CC 9.0, and CC (2014) 10.0.ParticipantI know we've already talked about this bug, but I just noticed that you'd cross-posted it to the InDesignSecrets forum. So to close this out as well I'll repost my earlier email response to you.
We have identified what we believe to be a bug in Adobe InDesign whereby it has a fatal crash with a null pointer exception when:
- you insert a specific number of columns into a table; and
- the table insertion point intersects with a merged cell (row).
The specific scenario is inserting a number of columns greater than the count of existing columns opposite of the insertion point (side). For example: in a 4-column table if you select column 3 to insert 1 column to the left, the insertion is successful. But if you instead insert more than 1 column to the left, InDesign crashes. Alternately, if you inserted 2 columns to the right, the insertion is successful. But if you instead insert more than 2 columns to the right, InDesign crashes.
We are tracking this internally as bug 4819, but we believe this to be a failure within Adobe InDesign—the exception/crash occurs when AutoFit calls the method GetFrameIndexContaining(theTextPosition) on the existing InDesign interface IFrameList. We are also investigating whether we can access the underlying frame information via alternate methods that do not result in a fatal null pointer exception.
As a workaround, please temporarily disable AutoFit via the Preferences → Typefi → AutoFit Preferences when adding/inserting columns within tables with merged columns (note: this bug affects any table, not just tables within an AutoFit-enabled text frame).
-
AuthorPosts