InDesign 2022 17.3 - HIGH CPU when idle

New Here ,
Jul 26, 2022 Jul 26, 2022

Copy link to clipboard

Copied

I'm using a 16" M1 Max MacBook Pro with 32GB of ram and 2TB SSD. When InDesign is idle, it uses 30-40% doing absolutely nothing and hidden in the background. It's also like this on my other Mac. Any ideas?

Screen Shot 2022-07-26 at 11.03.09 AM.png

TOPICS
Bug , Performance

Views

70

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
community guidelines
Adobe Employee ,
Jul 26, 2022 Jul 26, 2022

Copy link to clipboard

Copied

Hi @curious777 ,

 

Sorry to hear about the trouble. Please try the suggestions shared here https://community.adobe.com/t5/indesign-discussions/re-indesign-cc-2018-high-cpu-usage-on-a-macbook-... and let us know if this helps or if you need any further assistance.

 

Regards

Rishabh

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
community guidelines
New Here ,
Jul 26, 2022 Jul 26, 2022

Copy link to clipboard

Copied

That did not help.

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
community guidelines
Adobe Employee ,
Jul 27, 2022 Jul 27, 2022

Copy link to clipboard

Copied

Thanks for trying. Please try turning off GPU performance from InDesign preferences and let us know if that makes a difference. 

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
community guidelines
Guide ,
Jul 28, 2022 Jul 28, 2022

Copy link to clipboard

Copied

Open Applications >> Utilities >> Activity Viewer

Select InDesign

From the fly-out menu "(…)" select first action "Analyse Process"

This will basically take snapshots from execution for some thousand times and record the locations within the code - repeats will cause higher numbers, where you can further drill down or collapse irrelevant parts.

InDesign has plenty threads that will just sit around and do nothing waiting on some system call with a high number. Ignore them.

Remaining may be interesting ones that will jump back and forth between multiple code locations (lower numbers each, but not down to 1), you will recognize the pattern.

Since InDesign is nicely split across many internal plug-ins, code locations give a general clue about the component involved - is it fonts, is it some communication, printing?

Copy-Paste that section e.g. into pastebin.com and share the link here.

 

Note that we above have already ruled out CEP extenions, those would eventually show in other processes.

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
community guidelines
Guide ,
Jul 28, 2022 Jul 28, 2022

Copy link to clipboard

Copied

LATEST

The following screenshot shows InDesign at very low activity, some CPU cycles used for drawing an icon in response to any event, maybe a mouse move. I used the Sichern... / Save button to produce a text version, matching section below.Bildschirmfoto 2022-07-29 um 05.44.12.png

 

+ 49 -[NSApplication run] (in AppKit) + 636 [0x189bb6278]
+ ! 49 -[NSApplication _handleEvent:] (in AppKit) + 76 [0x189fee4f8]
+ ! 41 ??? (in Application UI) load address 0x11a2dc000 + 0x1928b4 [0x11a46e8b4]
+ ! : 37 ??? (in AppFramework) load address 0x119234000 + 0x67868 [0x11929b868]
+ ! : | 37 ??? (in AppFramework) load address 0x119234000 + 0x67c24 [0x11929bc24]
+ ! : | 20 ??? (in Application UI) load address 0x11a2dc000 + 0x1680d0 [0x11a4440d0]
+ ! : | + 20 ??? (in Application UI) load address 0x11a2dc000 + 0x10c890 [0x11a3e8890]
+ ! : | + 20 ??? (in Application UI) load address 0x11a2dc000 + 0x10c268 [0x11a3e8268]
+ ! : | + 20 ??? (in Application UI) load address 0x11a2dc000 + 0x52abc [0x11a32eabc]
+ ! : | + 18 ??? (in Application UI) load address 0x11a2dc000 + 0x52b74 [0x11a32eb74]
+ ! : | + ! 18 DVPanelView::DoPostCreate() (in DV_WidgetBinLib.dylib) + 20 [0x10552d8dc]
+ ! : | + ! 17 DVBasePanelView::DoPostCreate() (in DV_WidgetBinLib.dylib) + 156 [0x105547810]
+ ! : | + ! : 17 DVPanelView::DoPostCreate() (in DV_WidgetBinLib.dylib) + 20 [0x10552d8dc]
+ ! : | + ! : 17 DVBasePanelView::DoPostCreate() (in DV_WidgetBinLib.dylib) + 156 [0x105547810]
+ ! : | + ! : 17 DVPanelView::DoPostCreate() (in DV_WidgetBinLib.dylib) + 20 [0x10552d8dc]
+ ! : | + ! : 13 DVBasePanelView::DoPostCreate() (in DV_WidgetBinLib.dylib) + 44 [0x1055477a0]
+ ! : | + ! : | 13 ??? (in ObjectModelLib.dylib) load address 0x109dbc000 + 0x47310 [0x109e03310]
+ ! : | + ! : | 13 ??? (in ObjectModelLib.dylib) load address 0x109dbc000 + 0x3c358 [0x109df8358]
+ ! : | + ! : | 13 DVPanelControlData::ReadWrite(IPMStream*, IDType<ImplementationID_tag>) (in DV_WidgetBinLib.dylib) + 196 [0x10552c510]
+ ! : | + ! : | 13 AbstractPanelControlData::QueryWidget(IDataBase*, IDType<UID_tag> const&) (in DV_WidgetBinLib.dylib) + 364 [0x1055300a4]
+ ! : | + ! : | 13 DataBase::Instantiate(IDType<UID_tag>, IDType<PMIID_tag>) (in DataBaseLib.dylib) + 180 [0x109005a84]
+ ! : | + ! : | 12 ??? (in ObjectModelLib.dylib) load address 0x109dbc000 + 0x47310 [0x109e03310]
+ ! : | + ! : | + 10 ??? (in ObjectModelLib.dylib) load address 0x109dbc000 + 0x3c358 [0x109df8358]
+ ! : | + ! : | + ! 9 DVIconSuiteBaseView::ReadWrite(IPMStream*, IDType<ImplementationID_tag>) (in DV_WidgetBinLib.dylib) + 116 [0x1055cdad0]
+ ! : | + ! : | + ! : 8 DVIconSuiteView::LoadIcon(unsigned int const&, IDType<PluginID_tag> const&) (in DV_WidgetBinLib.dylib) + 24 [0x105555034]

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
community guidelines