Restart recommended We detected that your session has unusually high memory - New Outlook

Anonymous
2024-10-10T12:37:46+00:00

New outlook feels sluggish, after a few minutes and then after a minute or two a message popup "Restart recommended We detected that your session has unusually high memory". Restart and it works again for a few minutes. feels like a bug or memoryleak. After updates applied today. (Fully updates system)

Running classic outlook solves the problem, but just a heads up. If no one has a fix :)

1.2024.1002.100 (Production)
Klientversion is 20240927008.14.

WebView2-versionen er 129.0.2792.79.

Outlook | Windows | New Outlook for Windows | For home

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

52 answers

Sort by: Newest
  1. Anonymous
    2024-10-10T18:59:00+00:00

    where are you getting this information?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-10-10T18:56:59+00:00

    In Pennsylvania also and this just started happening today. Using Outlook (New) desktop app, a restart will fix for a short time but then memory usage builds up quickly (anywhere from 10-20 minutes).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-10-10T18:41:36+00:00

    Same issue here in Arkansas

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-10-10T18:38:12+00:00

    Microsoft announced that the problem is fixed. Restart your Outlooks / refresh your browsers if you had had switched to browser based Outlooks like me during the day. It's been 10 minutes and no CPU/Memory spikes so far. I am using the "New Outlook" toggled ON

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more