[ITEM]
23.02.2020

Outlook For Mac 16.10 High Cpu Usage

64

An apparently common issue with Outlook for Mac 2011 is crazily highCPU usage, enough to spin up the fans on a desktop machine or drainthe battery on a laptop, when Outlook really shouldn’t be doinganything.

Exchange 2016 High CPU usage on a exchange 2016 after migration from exchange 2010. Hardware Setup: VM (Windows Server 2016), 2 virtuell sockets with 2 processors each, 32gb of ram running on a ProLiant DL360p gen8, all behind a firewall. (top 13 are mac users with office for mac). Configure Outlook Anywhere.

If you do some Googling, you’ll find a lot of people complaining andalmost as many recommended solutions. Updating to a version after14.2 is a typical suggestion, as is deleting and rebuilding your mailaccounts (ugh, no thanks).

Keeping Outlook up to date isn’t a bad idea, but the problem stillpersisted with the latest version as of today (14.4.3).

In my case, the high CPU usage had something to do with my GmailIMAP account, which is accessed from Outlook alongside my Exchangemailbox. Disabling the Gmail account stopped the stupid CPU usage,but that’s not really a solution.

What did work was using the Progress window to see what Outlook was upto whenever the CPU pegged. As it turned out, there was a particularIMAP folder — the ‘Starred’ folder, used by both Gmail and Outlookfor starred and flagged messages, respectively — which was beingconstantly refreshed by Outlook. It would upload all the messages inthe folder to Gmail, then quiesce for a second, then do it overagain. Over and over.

Outlook’s IMAP implementation is just generally bad, and this seemsto happen occasionally without warning. But the Outlook engineersseem to have anticipated it, because if you right-click on an IMAPfolder, there’s a helpful option called “Repair Folder”. If you useit on the offending folder, it will replace the contents of the localIMAP store with the server’s version, and break the infinite-refresh cycle.

Dynamsoft Webcam SDK provides JavaScript APIs that enable you to easily capture images and video streams from USB Video Class (UVC) compatible webcams from within a browser. With the browser-based Webcam library, you can capture a live video stream into a container and grab an image with a couple lines of code in your web application.Feature Highlights:. Webcam control for mac.

So, long story short; if you have high-CPU issues with Outlook Mac,try the following:

  1. Update Outlook using the built-in update functionality. See ifthat fixes the issue.
  2. Use the Progress window to see what Outlook is doing at times whenthe CPU usage is high. Is it refreshing an IMAP folder?
  3. If so, use the Repair Folder option on that IMAP folder, but beaware that any local changes you’ve made will be lost.

And, of course, lobby your friendly local IT department to usesomething that sucks less than Exchange.

0 Comments, 0 Trackbacks

[/technology] permalink

Can't believe Outlook Mac kept giving me issues. This is the 2nd major one in a week.
Anyways, the issue was that after I did the previous fix (check out my previous post), Outlook was ok for a while. However, just after a couple of days using it, I noticed that it slowed down tremendously. Checking the Activity Monitor, it showed that Outlook was using up to 300% of the CPU resource. While I was still able to use it, it was terribly slow given that it was doing something heavy in the background.
Googling failed to come up with any solutions, apart from reinstalling everything. So I followed the instructions from this post:
https://community.spiceworks.com/topic/1607887-outlook-for-mac-v15-22-high-cpu-usage
Here's the excerpt:

Description of issue:
Hello all,
Yesterday I updated my Office applications for my MacBook Pro (running OS 10.10.5) to the version 15.22. Ever since then, my Outlook application has been using pretty much all of my CPU resources. It doesn't happen right away, normally takes an hour or so for it to start hogging them all, but once it happens Outlook becomes unusable and I have to Force Quit everything. In Activity Monitor it's showing CPU usage at somewhere like 780%, which is just absolutely bonkers.
Is anyone else running into this issue with the Office update? I haven't seen this happen with any other Office apps, but to be fair I hardly use anything but Outlook. Would really appreciate any advice or tips you could throw my way

Solution:
The Microsoft rep was not able to help me with this issue, but the solution I found myself was just to uninstall and reinstall the Office 365 suite. To uninstall, I moved all Office programs to the Trash, emptied it, then navigated to ~LibraryContainers and then deleted all of the pertinent com.microsoft folders, as well as all Microsoft folders located in ~LibraryGroup Containers (UBF8T346.. etc). Then I reinstalled from my Office 365 login page, and have yet to reproduce the issue.
Hope that helps.

I did the above and reinstalled an older version (v15.39). That's fine by me cause at least it's usable again. Maybe it's time to turn off the Fast Insider updates.
[/ITEM]
[/MAIN]
23.02.2020

Outlook For Mac 16.10 High Cpu Usage

2

An apparently common issue with Outlook for Mac 2011 is crazily highCPU usage, enough to spin up the fans on a desktop machine or drainthe battery on a laptop, when Outlook really shouldn’t be doinganything.

Exchange 2016 High CPU usage on a exchange 2016 after migration from exchange 2010. Hardware Setup: VM (Windows Server 2016), 2 virtuell sockets with 2 processors each, 32gb of ram running on a ProLiant DL360p gen8, all behind a firewall. (top 13 are mac users with office for mac). Configure Outlook Anywhere.

If you do some Googling, you’ll find a lot of people complaining andalmost as many recommended solutions. Updating to a version after14.2 is a typical suggestion, as is deleting and rebuilding your mailaccounts (ugh, no thanks).

Keeping Outlook up to date isn’t a bad idea, but the problem stillpersisted with the latest version as of today (14.4.3).

In my case, the high CPU usage had something to do with my GmailIMAP account, which is accessed from Outlook alongside my Exchangemailbox. Disabling the Gmail account stopped the stupid CPU usage,but that’s not really a solution.

What did work was using the Progress window to see what Outlook was upto whenever the CPU pegged. As it turned out, there was a particularIMAP folder — the ‘Starred’ folder, used by both Gmail and Outlookfor starred and flagged messages, respectively — which was beingconstantly refreshed by Outlook. It would upload all the messages inthe folder to Gmail, then quiesce for a second, then do it overagain. Over and over.

Outlook’s IMAP implementation is just generally bad, and this seemsto happen occasionally without warning. But the Outlook engineersseem to have anticipated it, because if you right-click on an IMAPfolder, there’s a helpful option called “Repair Folder”. If you useit on the offending folder, it will replace the contents of the localIMAP store with the server’s version, and break the infinite-refresh cycle.

Dynamsoft Webcam SDK provides JavaScript APIs that enable you to easily capture images and video streams from USB Video Class (UVC) compatible webcams from within a browser. With the browser-based Webcam library, you can capture a live video stream into a container and grab an image with a couple lines of code in your web application.Feature Highlights:. Webcam control for mac.

So, long story short; if you have high-CPU issues with Outlook Mac,try the following:

  1. Update Outlook using the built-in update functionality. See ifthat fixes the issue.
  2. Use the Progress window to see what Outlook is doing at times whenthe CPU usage is high. Is it refreshing an IMAP folder?
  3. If so, use the Repair Folder option on that IMAP folder, but beaware that any local changes you’ve made will be lost.

And, of course, lobby your friendly local IT department to usesomething that sucks less than Exchange.

0 Comments, 0 Trackbacks

[/technology] permalink

Can't believe Outlook Mac kept giving me issues. This is the 2nd major one in a week.
Anyways, the issue was that after I did the previous fix (check out my previous post), Outlook was ok for a while. However, just after a couple of days using it, I noticed that it slowed down tremendously. Checking the Activity Monitor, it showed that Outlook was using up to 300% of the CPU resource. While I was still able to use it, it was terribly slow given that it was doing something heavy in the background.
Googling failed to come up with any solutions, apart from reinstalling everything. So I followed the instructions from this post:
https://community.spiceworks.com/topic/1607887-outlook-for-mac-v15-22-high-cpu-usage
Here's the excerpt:

Description of issue:
Hello all,
Yesterday I updated my Office applications for my MacBook Pro (running OS 10.10.5) to the version 15.22. Ever since then, my Outlook application has been using pretty much all of my CPU resources. It doesn't happen right away, normally takes an hour or so for it to start hogging them all, but once it happens Outlook becomes unusable and I have to Force Quit everything. In Activity Monitor it's showing CPU usage at somewhere like 780%, which is just absolutely bonkers.
Is anyone else running into this issue with the Office update? I haven't seen this happen with any other Office apps, but to be fair I hardly use anything but Outlook. Would really appreciate any advice or tips you could throw my way

Solution:
The Microsoft rep was not able to help me with this issue, but the solution I found myself was just to uninstall and reinstall the Office 365 suite. To uninstall, I moved all Office programs to the Trash, emptied it, then navigated to ~LibraryContainers and then deleted all of the pertinent com.microsoft folders, as well as all Microsoft folders located in ~LibraryGroup Containers (UBF8T346.. etc). Then I reinstalled from my Office 365 login page, and have yet to reproduce the issue.
Hope that helps.

I did the above and reinstalled an older version (v15.39). That's fine by me cause at least it's usable again. Maybe it's time to turn off the Fast Insider updates.