InDesign v 14.0.2

We use Drive File Stream for all of our file storing - which has been working great until last week when opening certain files made InDesign crash repeatedly. I have tried to save as an IDML, download locally and still have the crashing problem.

When I go to open the file it will just freeze the application window, no panels visable and just the spinning Mac ball. Force quit and then reopen InDesign - then it freezes again each time upon reopening, before trying to open any files and I have to force quit again. The second time trying to reopen is successful.

Drive file stream is working fine for most other files.

We've been making a large catalogue pricelist for over 13 years using indesign.

We're now stuck on the 2017 (12.1.0) version.
We want to update it, but in the latest version, importing our pricelist from excel into a table, slows the whole thing down to an unworkable speed.

info:
the table is around 13000 rows by 10 columns. so not small.
it does import in the 2017 version. slow to import in both, but can use and work on after import in 2017 version.
2019, freezes when scroll used, and take 1-3 mins to unfreeze. Scroll again or do anything much else and freezes again.
I can see it's using 100% of 1 CPU core. And I know Indesign is built in a way that it can only use 1 CPU core! (please fix this!!!!)

Code below works fine on Windows and CC 2018 on Mac. But CC 2019 Mac it hangs the app once clicking the OK button in window 2. I've tried three different Macs including Mojave and High Sierra. All the same result. Pretty sure it's not just me. This bug has broken a number of my scripts that present a secondary window for saving settings.

var w1 = new Window("dialog", "Window 1");
var btnOpenWindow2 = w1.add("button", undefined, "Open Window 2");
var btnOk1 = w1.add("button", undefined, "OK");
btnOpenWindow2.onClick = function () {
openWindow2();
};
btnOk1 = function () {
w1.close();
};
w1.show();


function openWindow2 () {
var w2 = new Window("dialog", "Window 2");
var btnOk2 = w2.add("button", undefined, "OK");
btnOk2.onClick = function () {
w2.close();
};
w2.show();
}

We are developping a plugin for inDesign and while testing a new feature on a Mac we noticed that sometimes InDesign was crashing. We managed to reproduce this bug in a very simple indesign script that make inDesign crash 100% of the time and I'm looking for a way to get around this inDesign bug.

The crash occurs when we programatically add an htmlItem to a pageItem then close the document too quicky, It's only on Mac, doing that on windows works perfectly. The crash error seems to be a memory usage problem on inDesign's side.

Here is the script code :

var document = app.activeDocument;
var sourcePageItem = document.allPageItems[0];

sourcePageItem.htmlItems.add(
document.activeLayer,
LocationOptions.AT_END,
sourcePageItem,
{
geometricBounds: sourcePageItem.geometricBounds,
htmlContent: '<b>Hello</b>',
}
);

document.close(SaveOptions.NO);

other observations :

-Doing a sourcePageItem.htmlItems[0].remove(); to remove the htmlItem after adding it doesn't change anything, so the problem comes from using the function htmlItems.add() and not having an htmlItem in the document.
-Delaying the close by using $.sleep(5000) before fix the crash, but we can't rely on it as the delay needed increase with the number of htmlItems added and it might be different from a computer to another due to performances.
-Saving the document or not doesn't change anything


I've added my clean document with just a rectangle frame, the script and the crash report on this url : https://we.tl/t-uFpX658s0o since we can't add an indeed file to the post

If there is no way to fix it, do you have an idea to get around this inDesign bug ?

We are developping a plugin for inDesign and while testing a new feature on a Mac we noticed that sometimes InDesign was crashing. We managed to reproduce this bug in a very simple indesign script that make inDesign crash 100% of the time and I'm looking for a way to get around this inDesign bug.

The crash occurs when we programatically add an htmlItem to a pageItem then close the document too quicky, It's only on Mac, doing that on windows works perfectly. The crash error seems to be a memory usage problem on inDesign's side.

Here is the script code :

var document = app.activeDocument;
var sourcePageItem = document.allPageItems[0];

sourcePageItem.htmlItems.add(
document.activeLayer,
LocationOptions.AT_END,
sourcePageItem,
{
geometricBounds: sourcePageItem.geometricBounds,
htmlContent: '<b>Hello</b>',
}
);

document.close(SaveOptions.NO);

other observations :

-Doing a sourcePageItem.htmlItems[0].remove(); to remove the htmlItem after adding it doesn't change anything, so the problem comes from using the function htmlItems.add() and not having an htmlItem in the document.
-Delaying the close by using $.sleep(5000) before fix the crash, but we can't rely on it as the delay needed increase with the number of htmlItems added and it might be different from a computer to another due to performances.
-Saving the document or not doesn't change anything


I've added the script, my clean document with just a rectangle frame and the crash report with this post.

If there is no way to fix it, do you have an idea to get around this inDesign bug ?

Using version 14.0.2 x64 under Windows 10.

Working on a 356-page book. Three types of crashes occur consistently:

1 - When I export to PDF.
2 - When I add pages, usually in increments of 10.
3 - When I switch between single-page layout and 2-page spread layout.

After every crash, when I go to open the file, inDesign offers to auto recover the file. When I say yes, InDesign warns me that the file might be corrupt. I always open anyway. After 3 months working on this book, I can't afford to start over, so I hope for the best.

Three of the crashes have caused significant problems.

1 - The first 38 pages had been deleted. I had to completely redo them.
2 - The even-page master had been applied to all pages. I had to highlight all the odd pages and re-apply the odd-page master.
3 - Tonight's crash resulted in master pages designations and therefore page numbers on all 356 pages being deleted. I have to highlight all the odd pages, re-apply the odd-page master, highlight all the even pages, and re-apply the even-page master.

I have been using InDesign since the PageMaker days but my experience over these past three months is going to cause me to look elsewhere.... Word, Blurb, etc.