Highlighted

InDesign Update (12.1.0.56) Crashes with JavaScript Tabbed Dialogs

Explorer ,
Apr 25, 2017

Copy link to clipboard

Copied

Just recently updated my CC 2017 Macintosh to build 12.1.0.56 (the one with the updated user interface).

We have many JavaScripts that use tabbed dialog windows. In this build of InDesign, the application crashes when any tabbed JavaScript dialog window is closed. Sample code below can be used to demonstrate the problem. Just run it and click the OK button and InDesign crashes.

    var w = new Window ("dialog", "Test", undefined, {resizeable:false,closeButton:true});

    var mainPanel = w.add('tabbedpanel');

    var tab1 = mainPanel.add('tab', undefined, "Setup");

    var okButton = w.add("button", undefined, "OK" ,{name:'ok'});

    okButton.onClick = function () {

            w.close();

    }

    w.show();   

Have tried resetting InDesign preferences with no help. A copy of the crash log is shown below.

Anyone have a workaround for this?

Thanks,

JK

----------------- Hardware Setup ----------------------------

Macbook Pro

OS 10.10.5

2.6 GHz

16 GB Memory

----------------- Partial Crash Log ----------------------------

Process:               Adobe InDesign CC 2017 [23422]

Path:                  /Applications/Adobe InDesign CC 2017/Adobe InDesign CC 2017.app/Contents/MacOS/Adobe InDesign CC 2017

Identifier:            com.adobe.InDesign

Version:               12.1.0.56 (12100)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Adobe InDesign CC 2017 [23422]

User ID:               501

Date/Time:             2017-04-25 18:08:02.391 -0500

OS Version:            Mac OS X 10.10.5 (14F27)

Report Version:        11

Anonymous UUID:        DFA7EE4A-9732-C495-2617-A20C391030F0

Sleep/Wake UUID:       6F497237-9B1E-4564-8A0C-C04EEC8805AC

Time Awake Since Boot: 42000 seconds

Time Since Wake:       15000 seconds

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:

-->

    __TEXT                 000000010b416000-000000010b420000 [   40K] r-x/rwx SM=COW  /Applications/Adobe InDesign CC 2017/Adobe InDesign CC 2017.app/Contents/MacOS/Adobe InDesign CC 2017

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   com.adobe.dvaui.framework     0x000000010c0de73d dvaui::controls::UI_TabItem::GetTextWidth() const + 173

1   com.adobe.dvaui.framework     0x000000010c0de11e dvaui::controls::UI_TabItem::UI_UpdateLayout() + 606

2   com.adobe.dvaui.framework     0x000000010c0bf9e1 dvaui::controls::UI_TabItem::UpdateUIState() + 385

3   com.adobe.dvaui.framework     0x000000010c0ca993 dvaui::controls::UI_TabWell::SetFrontmostAndBroadcast(long, bool, long) + 659

4   com.adobe.dvaui.framework     0x000000010c0b635f dvaui::controls::UI_TabContainer::BringTabToFront(unsigned long) + 95

5   com.adobe.dvascriptui.framework 0x000000011b3b64b1 ScriptUI::DroverTabbedPanel::setSelection(ScCore::LiveObject*) + 81

6   com.adobe.dvascriptui.framework 0x000000011b3b610d ScriptUI::DroverTabbedPanel::removeTab(ScriptUI::ElementBase&, bool) + 301

7   com.adobe.dvascriptui.framework 0x000000011b3b7a87 ScriptUI::DroverTabView::invalidate() + 39

8   com.adobe.dvascriptui.framework 0x000000011b3cabb9 ScriptUI::ElementBase::invalidate() + 489

9   com.adobe.dvascriptui.framework 0x000000011b3ceb1f ScriptUI::ElementBase::removeChild(ScriptUI::ElementBase&) + 319

10  com.adobe.dvascriptui.framework 0x000000011b3caa54 ScriptUI::ElementBase::invalidate() + 132

11  com.adobe.dvascriptui.framework 0x000000011b3ceb1f ScriptUI::ElementBase::removeChild(ScriptUI::ElementBase&) + 319

12  com.adobe.dvascriptui.framework 0x000000011b3caa54 ScriptUI::ElementBase::invalidate() + 132

13  com.adobe.dvascriptui.framework 0x000000011b3caccf ScriptUI::ElementBase::release() const + 47

14  com.adobe.AdobeExtendScript   0x000000011b1cf187 ScScript::InitTerm::atExit(void (*)()) + 8583

15  com.adobe.AdobeExtendScript   0x000000011b1d2aff ScScript::InitTerm::atExit(void (*)()) + 23295

16  com.adobe.AdobeExtendScript   0x000000011b1ced2c ScScript::InitTerm::atExit(void (*)()) + 7468

17  com.adobe.AdobeExtendScript   0x000000011b1d867d ScScript::InitTerm::atExit(void (*)()) + 46717

18  com.adobe.InDesign.Support for JavaScript 0x0000000122a57e33 0x122a55000 + 11827

19  com.adobe.InDesign.Support for JavaScript 0x0000000122a58993 0x122a55000 + 14739

20  com.adobe.InDesign.Support for JavaScript 0x0000000122a72e53 0x122a55000 + 122451

Just FYI this has been confirmed as a bug, reported by many customers. Only occurs with 12.1.0.56. We bit the bullet and just redesigned the dialogs to eliminate the tabbed panels. I am sure it will be fixed ... at some point.

Good to know that palette type might be a workaround but we need these to be modal in this case.

Thanks!

JK

TOPICS
Scripting

Views

2.0K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

InDesign Update (12.1.0.56) Crashes with JavaScript Tabbed Dialogs

Explorer ,
Apr 25, 2017

Copy link to clipboard

Copied

Just recently updated my CC 2017 Macintosh to build 12.1.0.56 (the one with the updated user interface).

We have many JavaScripts that use tabbed dialog windows. In this build of InDesign, the application crashes when any tabbed JavaScript dialog window is closed. Sample code below can be used to demonstrate the problem. Just run it and click the OK button and InDesign crashes.

    var w = new Window ("dialog", "Test", undefined, {resizeable:false,closeButton:true});

    var mainPanel = w.add('tabbedpanel');

    var tab1 = mainPanel.add('tab', undefined, "Setup");

    var okButton = w.add("button", undefined, "OK" ,{name:'ok'});

    okButton.onClick = function () {

            w.close();

    }

    w.show();   

Have tried resetting InDesign preferences with no help. A copy of the crash log is shown below.

Anyone have a workaround for this?

Thanks,

JK

----------------- Hardware Setup ----------------------------

Macbook Pro

OS 10.10.5

2.6 GHz

16 GB Memory

----------------- Partial Crash Log ----------------------------

Process:               Adobe InDesign CC 2017 [23422]

Path:                  /Applications/Adobe InDesign CC 2017/Adobe InDesign CC 2017.app/Contents/MacOS/Adobe InDesign CC 2017

Identifier:            com.adobe.InDesign

Version:               12.1.0.56 (12100)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Adobe InDesign CC 2017 [23422]

User ID:               501

Date/Time:             2017-04-25 18:08:02.391 -0500

OS Version:            Mac OS X 10.10.5 (14F27)

Report Version:        11

Anonymous UUID:        DFA7EE4A-9732-C495-2617-A20C391030F0

Sleep/Wake UUID:       6F497237-9B1E-4564-8A0C-C04EEC8805AC

Time Awake Since Boot: 42000 seconds

Time Since Wake:       15000 seconds

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:

-->

    __TEXT                 000000010b416000-000000010b420000 [   40K] r-x/rwx SM=COW  /Applications/Adobe InDesign CC 2017/Adobe InDesign CC 2017.app/Contents/MacOS/Adobe InDesign CC 2017

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   com.adobe.dvaui.framework     0x000000010c0de73d dvaui::controls::UI_TabItem::GetTextWidth() const + 173

1   com.adobe.dvaui.framework     0x000000010c0de11e dvaui::controls::UI_TabItem::UI_UpdateLayout() + 606

2   com.adobe.dvaui.framework     0x000000010c0bf9e1 dvaui::controls::UI_TabItem::UpdateUIState() + 385

3   com.adobe.dvaui.framework     0x000000010c0ca993 dvaui::controls::UI_TabWell::SetFrontmostAndBroadcast(long, bool, long) + 659

4   com.adobe.dvaui.framework     0x000000010c0b635f dvaui::controls::UI_TabContainer::BringTabToFront(unsigned long) + 95

5   com.adobe.dvascriptui.framework 0x000000011b3b64b1 ScriptUI::DroverTabbedPanel::setSelection(ScCore::LiveObject*) + 81

6   com.adobe.dvascriptui.framework 0x000000011b3b610d ScriptUI::DroverTabbedPanel::removeTab(ScriptUI::ElementBase&, bool) + 301

7   com.adobe.dvascriptui.framework 0x000000011b3b7a87 ScriptUI::DroverTabView::invalidate() + 39

8   com.adobe.dvascriptui.framework 0x000000011b3cabb9 ScriptUI::ElementBase::invalidate() + 489

9   com.adobe.dvascriptui.framework 0x000000011b3ceb1f ScriptUI::ElementBase::removeChild(ScriptUI::ElementBase&) + 319

10  com.adobe.dvascriptui.framework 0x000000011b3caa54 ScriptUI::ElementBase::invalidate() + 132

11  com.adobe.dvascriptui.framework 0x000000011b3ceb1f ScriptUI::ElementBase::removeChild(ScriptUI::ElementBase&) + 319

12  com.adobe.dvascriptui.framework 0x000000011b3caa54 ScriptUI::ElementBase::invalidate() + 132

13  com.adobe.dvascriptui.framework 0x000000011b3caccf ScriptUI::ElementBase::release() const + 47

14  com.adobe.AdobeExtendScript   0x000000011b1cf187 ScScript::InitTerm::atExit(void (*)()) + 8583

15  com.adobe.AdobeExtendScript   0x000000011b1d2aff ScScript::InitTerm::atExit(void (*)()) + 23295

16  com.adobe.AdobeExtendScript   0x000000011b1ced2c ScScript::InitTerm::atExit(void (*)()) + 7468

17  com.adobe.AdobeExtendScript   0x000000011b1d867d ScScript::InitTerm::atExit(void (*)()) + 46717

18  com.adobe.InDesign.Support for JavaScript 0x0000000122a57e33 0x122a55000 + 11827

19  com.adobe.InDesign.Support for JavaScript 0x0000000122a58993 0x122a55000 + 14739

20  com.adobe.InDesign.Support for JavaScript 0x0000000122a72e53 0x122a55000 + 122451

Just FYI this has been confirmed as a bug, reported by many customers. Only occurs with 12.1.0.56. We bit the bullet and just redesigned the dialogs to eliminate the tabbed panels. I am sure it will be fixed ... at some point.

Good to know that palette type might be a workaround but we need these to be modal in this case.

Thanks!

JK

TOPICS
Scripting

Views

2.0K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Apr 25, 2017 0
Adobe Community Professional ,
Apr 25, 2017

Copy link to clipboard

Copied

Hi John,

thank you for posting this.

Just tested your code on:


German CC 2017.1 version 12.1.0.56.
German Mac OSX 10.10.5

MacBook Pro from late 2011

I ran the code from the Scripts panel of InDesign and used a targetengine directive:


#targetengine test

Did not test to run it from the ESTK (ExtendScript Toolkit app).

Different results.

First try:

1. Ran it when no document was open.
Closed the dialog. No problem. No crash.

2. Opened a new unnamed document.

Ran it again. Answered the dialog: Crash

Second try:

Ok. Trashed the preferences. Restarted InDesign.

1. Added a new document. Saved it.
Run the script. No problem after closing the dialog.

2. Double-clicked the script again.

Instant crash without seeing the dialog.

My crash report looks the same…

Also did a test run with InDesign CS6 version 8.1.0 on the same machine.
No crash when I ran the script several times with or without documents open.

No idea how to avoid the crash…

Regards,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Adobe Community Professional ,
Apr 25, 2017

Copy link to clipboard

Copied

Hi John,

I hope Peter Kahrel stops by…

In the meanwhile I tested the code below where I redefined the panel every time I start the script.

This is working up to the point when I quit InDesign. Then InDesign is crashing. With the same crash report you experienced.

#targetengine test5

tabbedPanel();

function tabbedPanel()

{

    // At the start redefine the panel:

    var w = {};

    w = new Window("dialog", "Test" );

  

    w.resizeable = false ;

    w.closeButton = true;

  

    var mainPanel = w.add("tabbedpanel");

    mainPanel.preferredSize = [350,300];

  

    var tab1 = mainPanel.add("tab", undefined, "Setup");

    var okButton = w.add( "button" , undefined , "OK" , { name : "ok" } );

    okButton.onClick =

    function()

    {

        w.close();

    };

      

    w.show();

};

Regards,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 25, 2017 0
Explorer ,
Apr 26, 2017

Copy link to clipboard

Copied

Thanks so much for having a look. The snippet was as small as I could make it - in the actual code we do rebuild the tabs each time, but continues to crash. These scripts have been running flawlessly for a long time and work with all versions of InDesign that I have tested. It was only with this new CC 2017 build that the crashes begain, so assume this to be a bug with this build considering all the changes to the UI. We posted the incident to developer support as well. If I receive an answer I will post here.

Thanks again.

JK

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 26, 2017 0
Adobe Community Professional ,
Apr 26, 2017

Copy link to clipboard

Copied

Hi John,

which versions on InDesign did you test where the code is running without a crash?
And what is your OS version? Did ou try it on Windows, on Mac OSX or both?

Regards,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 26, 2017 0
Adobe Community Professional ,
Apr 26, 2017

Copy link to clipboard

Copied

Forget my question about the OS. You are on OSX 10.10.5. The crash report is showing this.


But it would be important to know, if it would crash on any of the other InDesign CC versions like CC version 9.3.0, CC 2014.2 or CC 2015.4.1. To complete the picture it would be good to know if you also tried InDesign CC 2017.0 version 12.0.0.81.

And if it would run without a crash on Windows…

Thanks,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 26, 2017 0
Adobe Community Professional ,
Apr 26, 2017

Copy link to clipboard

Copied

This is a 2017.1 bug, doesn't occur in earlier versions (not even 2017.0). The only workaround for now is to use a palette-type window, not a dialog.

P.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 26, 2017 2
Adobe Community Professional ,
Apr 26, 2017

Copy link to clipboard

Copied

Hi Peter,

thank you very much for that.

Just tested John's code and my little snippet from reply 2 with "palette" and "window" type of Window.

Both will not crash InDesign CC 2017.1.

But both have their issues if they should substitute a "dialog" type of Window.

"dialog" is modal, "palette" is non-modal.

So if the Window is waiting for an action of the user to proceed and the user is changing something in the document while the Window is waiting, answering controls of the Window could lead to errors, because the document is not anymore in the state after the user started the script.

"window" is also non-modal.

Same issues with "palette". And another big issue added for Mac OSX users:

A "window" type of Window could suddenly get stacked behind the application frame of InDesign on Mac OSX if the user is doing something else but using the controls of the Window. For example clicking the gray area of the application frame or the white area of a page or invoking an InDesign palette…

Regards,

Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 26, 2017 0
Adobe Community Professional ,
Apr 26, 2017

Copy link to clipboard

Copied

Another workaround could be to revert to InDesign CC 2017 version 12.0.0.81 until this bug is fixed.

How would one do this? See: 2017.1 back to 2017

At least we should write up the issue with the "dialog" type of Window and do a bug report here:

Feature Request/Bug Report Form

Regards,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 26, 2017 0
Adobe Community Professional ,
Apr 27, 2017

Copy link to clipboard

Copied

pkahrel  wrote

This is a 2017.1 bug, doesn't occur in earlier versions (not even 2017.0). The only workaround for now is to use a palette-type window, not a dialog.

P.

Hm…
Could we perhaps simulate a modal Window with a "palette" type (non-modal) Window using an eventlistener?

Can we stop the user doing anything in InDesign before answering a "palette" type Window?

Regards,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Community Professional ,
Apr 27, 2017

Copy link to clipboard

Copied

> At least we should write up the issue with the "dialog" type of Window and do a bug report here:

Did that last week

> Could we perhaps simulate a modal Window with a "palette" type (non-modal) Window using an eventlistener?

That's one possibility. Another option is to do your own tabs, much in the way that e.g. InDesign's Preferences window works.

See https://indd.adobe.com/view/a0207571-ff5b-4bbf-a540-07079bd21d75, p. 64.

P.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Community Professional ,
Apr 27, 2017

Copy link to clipboard

Copied

pkahrel  wrote

… See https://indd.adobe.com/view/a0207571-ff5b-4bbf-a540-07079bd21d75, p. 64.

Hi Peter,

do you refer to page 64 of the Publish Online document or to the page that is paginated with "64" ?

EDIT: Ah. I think, I get it.

It's the example on page 64-65 in the PDF.

Thank you for this!

Thanks,
Uwe

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
Adobe Community Professional ,
Apr 28, 2017

Copy link to clipboard

Copied

Yep. page.name is '64', page.offset is 67

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2017 0
Engaged ,
Apr 27, 2017

Copy link to clipboard

Copied

This bug is also biting my IDImposer and IDTextFitter customers who have upgraded to InDesign CC 2017.1 (12.1.0.56).  Same behavior: the script completes, but then InDesign crashes immediately afterward.  Doesn't happen with 2017.0 -- just 2017.1.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 27, 2017 0
MrTIFF LATEST
Engaged ,
May 26, 2017

Copy link to clipboard

Copied

I put in workarounds for the 2017.1 crasher problem in the IDImposer and IDTextFitter scripts (using multiple panels, stack alignment, and visibility-switching).  Users can download new versions at the InDesignTools.com website. - Stephen

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 26, 2017 1
Engaged ,
Apr 28, 2017

Copy link to clipboard

Copied

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 28, 2017 0
Adobe Community Professional ,
Apr 29, 2017

Copy link to clipboard

Copied

They're certainly related: in both cases the exception type is 'EXC_BAD_ACCESS (SIGSEGV)'. But the exceptions have different causes. In the crash log above you can see that the tabbedpanel is the problem (UI_TabItem), whereas the crash log in the other thread shows that it's nothing to do with the tabbed panel, looks like a problem with a text button.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Apr 29, 2017 0