Macbook M1 (Word / PowerPoint) Memory Leaks..

Anonymous
2023-09-18T09:50:49+00:00

Dear Community,

I have a persistent issue being discussed across various platforms, including Reddit and microsoft own community.
Despite numerous updates, the problem continues to exist, specifically on M1 MacBooks.

The core of the issue is that the MacBook tends to run out of memory and appears to resort to using storage as memory. This behavior results in notable performance issues with certain applications, especially Microsoft Office programs.

For excample, I recently encountered a situation where, while running PowerPoint version 16.78 on macOS version 13.0.1, my presentation encountered severe performance problems. On closer inspection, I found that Powerpoint was utilizing 58GB of RAM, which led to the program freezing.

It's imperative for us as a community to address this matter and find potential solutions.

Is there any working solution for this?

Thank you

Microsoft 365 Insider | PowerPoint | MacOS
Microsoft 365 Insider | PowerPoint | MacOS

A family of Microsoft presentation graphics products that offer tools for creating presentations and adding graphic effects like multimedia objects and special effects with text.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-11-29T10:53:13+00:00

Nothing worked. Even a full factory reset and different outlook versions.

I did end up to sell M1 and buy m2 which don’t have the issue now.

There is for sure a bug but only % of people are affected.

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments

19 additional answers

Sort by: Oldest
  1. Anonymous
    2023-09-18T12:42:15+00:00

    Hi Pavlo,

    Thanks for posting in the community. We are happy to help you.

    According to your description, the Office applications will utilize a lot of memory and may cause them to freeze. I have tested it on my side, but I can't reproduce the same situation. So, to troubleshoot and narrow down the situation, I recommend you try the following suggestions, then check again.

    1. Please try to move the related cache folder to Desktop, then check again

    a. Close and quit Word and PowerPoint

    b. Use Finder, press Shift + Command + G, copy and paste the path ~/Library/Containers/, find and move the folder Microsoft Word and the folder Microsoft PowerPoint to Desktop, then run Word/PowerPoint and check again.

    1. If the situation still happens, please switch to another Mac user profile (if you don’t have another Mac user profile, please create a new Mac user profile, then switch to the new user profile), run Word/PowerPoint, and check again.

    We look forward to your response. Thanks for your cooperation.

    Sincerely,

    George | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments
  2. Bob Jones AKA CyberTaz MVP 437.7K Reputation points
    2023-09-18T14:30:21+00:00

    For your consideration:

    You're running a Beta version of an Office update [expected to be problematic] on an out-of-date build of a fairly new operating system known to have issues. [Ventura is now at 13.5.2] Perhaps that has something to do with it. The OS handles memory management on Macs.

    FWIW, I've been using an M1 MBP for nearly 2 years without having any such issues. However, I've avoided Ventura due to its ongoing issues.

    Was this answer helpful?

    0 comments No comments
  3. Jim G 134K Reputation points MVP
    2023-09-18T17:58:05+00:00

    Hi

    Is it possible for you to share a sanitized version of the file for testing?

    Why a sample file is important for troubleshooting - - - - - - - and how to do it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-09-18T18:08:58+00:00

    hey,

    The reason I opted for the Beta software was due to a persistent issue in the stable version. However, it appears that the problem persists even in the Beta version.
    Im currently testing the solution proposed by George to see if I can reproduce the issue. If I can, my plan is to capture a memory dump and save it to an external drive for further analysis.

    This issue is only specific to M1 MacBooks, as I have two of them, both having the same problem.
    Interestingly, my new M2 MacBook Air and Pro does not seem to be affected by this issue.

    Was this answer helpful?

    0 comments No comments