Windows successfully diagnosed a low virtual memory condition

Category:

  • Компьютеры
  • Cancel

В винде своп отключать нельзя. Я б даже больше сказал, ручное управление не имеет смысла, только system managed. Это, в принципе, всё что вам нужно знать о свопе.

Опущу предысторию как я докатился до такой жизни, перейду сразу к деталям. Ключевой момент в нашем повествовании — выделение памяти в винде гарантированное. Т.е. если вы запросили сотни гигабайт и система вам не ответила отказом — значит можно смело эти сотни гигабайт пользовать и никто их у вас не отберёт пока сами не вернёте. Здесь есть коренное отличие от линуксов, в которых память выделяется по оптимистичному сценарию, можно всем пообещать золотые горы, а там уже как получится. Оба подхода имеют свои плюсы и минусы и оба имеют полное право на жизнь. Но вернёмся к винде. Т.к. компьютер у нас не резиновый, то существует верхний предел, больше которого система выделить памяти просто не может, и называется он у нас Commit Limit. Посмотреть его можно в Task manager, на закладке Performance, выбираем граф Memory и внизу буде Commited xx,x/yy,y GB. Вот второе число это и есть этот самый лимит, по сути это сумма физической памяти и всех свопов. Первое же число показывает Commit Charge — количество виртуальной памяти которые приложения зарезервировали у системы. Это именно резерв, ибо реальное выделение страницы памяти происходит только при обращении к ней.

А теперь представим гипотетическую ситуацию. Вы начитались умных статей в интернетах и отключили своп, типа у меня 32gb памяти, зачем мне этот рудимент? Потом запускаете всякие приложения которые память выделяют и не пользуют. Что в итоге видно в Task Manager:

  • Memory in use: 8,4 GB
  • Commit charge: 14,9 GB

В принципе памяти хватает, но потом запустили второе приложение, третье, в первом открыли большой проект, etc. и тут выскакивает сообщение что ресурсы кончились. Если быстро не среагировать, то у меня через 10-15 сек просто гаснут экраны и система перестаёт отвечать на запросы. Единственный выход — перезагрузка. После чего в логе находим запись от Microsoft-Windows-Resource-Exhaustion-Detector: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: <список 3-4 особо ценных приложений>. В Details:

  <SystemCommitLimit>35378827264</SystemCommitLimit> 
  <SystemCommitCharge>35239473152</SystemCommitCharge> 
  <PhysicalMemorySize>34305085440</PhysicalMemorySize> 
  <PhysicalMemoryUsage>21225635840</PhysicalMemoryUsage>

Видно что physical memory у нас ещё 13gb есть, а вот commit charge уже «кончился», система захлёбывается и становится непредсказуемой.

Источник

Platform Notice: Data Center Only — This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Windows is reporting a low virtual memory condition for the Jira Tomcat process:

1
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: tomcat8.exe.x64

Environment

Jira running in a virtual Windows environment.

Diagnosis

  • Slow page loading or other performance issues.

  • Repeated low virtual memory conditions were reported on the Windows Event Viewer.

  • A high percentage of swap space is used which can be found in the <total-swap-space>  and <free-swap-space>  in the Support Zip.

Cause

Java will use more RAM outside of the allocated heap as outlined in Run Jira Server in a virtualized environment. Excessive memory overcommitment can cause the OS to read/write memory to disk which can introduce performance issues.

Solution

A number of steps can be taken to resolve this behavior:

  1. Review the Jira applications installation requirements and heap usage to increase the Jira application memory by small amounts (256mb) to verify if the problem is still occurring.

  2. Repair Windows system files.

  3. Increase the minimum page size of the paging file.

If the issue persists after taking these steps, please reach out to Atlassian Support with a Support Zip from your environment.

Updated on

February 28, 2025

Was this helpful?

It wasn’t accurateIt wasn’t clearIt wasn’t relevant

Still need help?

The Atlassian Community is here for you.

Источник

Windows 10: Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost…

Discus and support Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost… in Windows 10 Gaming to solve the problem; HelloI have around 27 PCs on a site that intermittently experience software crashes a few times a week each. My software is a unity standalone build….
Discussion in ‘Windows 10 Gaming’ started by Joe Hutchinson, Feb 7, 2025.

  1. Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost…

    HelloI have around 27 PCs on a site that intermittently experience software crashes a few times a week each. My software is a unity standalone build. After further investigation, it seems that many of these crashes are caused by ‘System out of memory’ issues. Looking at the event log, I got multiple Resource-Exhaustion-Detector events for low virtual memory condition. One of them is the following:Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory:

    :)

  2. Windows successfully diagnosed a low virtual memory condition ?

    Teams kept crashing so I took a look at the event log and found this message just before it crashed.

    Any idea why Unarchiver.exe (which I assume was something to do with 7zip) is using so much virtual memory? that’s 2.47Gb

    I’ve uninstalled 7zip but I keep getting the same issue, Windows Defender and Malewarebytes can’t find anything, extremely frustrating to lose connection in meetings due to a random issue like this.

    Any help would be appreciated.

  3. Windows successfully diagnosed the condition of no virtual memory.

    Hi, AleksanderBR

    Welcome to Microsoft Community.

    We understand that you are experiencing issues related to virtual memory. There are times when Windows automatically allocates to virtual memory may not be sufficient for you to use certain software, in this case, you can try to set it manually:

    1. Open System Properties:

    • Right-click on «This computer» or «My computer» icon and select «Properties».

    2. Access Advanced System Settings:

    • In the System Properties window, click «Advanced System Settings» on the left side.

    3. View the performance settings:

    • Under the «Advanced» tab of the «System Properties» window, click «Settings» in the «Performance» section.

    4. Open the virtual memory settings:

    • In the «Performance Options» window, click on the «Advanced» tab, then locate the «Virtual Memory» section and click «Change». Click «Change».

    Adjust the virtual memory to the size you want to use.

    Furthermore, you can submit your ideas and suggestions about Virtual memory through the Feedback Hub, and the development team will regularly review submissions for ideas or fixes.

    Please share the feedback link here after submitting as it will allow others on the forum to vote for your submission, including me. More votes will lead to more visibility and higher priority to the development team.

    Best Regards

    Nicholas.Z| Microsoft Community Support Specialist

  4. Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost…

    How to deal with low virtual memory conditions

    I started having problems on my Windows 10 system about 2 weeks ago and find myself rebooting every few days because things are crashing. When I look in the event viewer I see a lot of repeats of warning messages that look like this:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Unpacker.exe (6288) consumed 2462076928 bytes, coldfusion.exe (5876) consumed 607285248 bytes, and BlueIris.exe (5500) consumed 539377664
    bytes.

    In the same area of the event viewer there are a lot of hard errors of services failing.

    I have no idea what unpacker.exe is but I do know about ColdFusion and Blue Iris and they are valid for my system. Is unpacker.exe something that Microsoft runs? I cannot find it on a scans of my C or D drive and when I run Malware Bytes it doesn’t bring
    this up as an issue.

    If unpacker is invalid, how do I get rid of it. If it is valid, why is it using up the virtual storage?

Thema:

Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost…

  1. Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost… — Similar Threads — successfully diagnosed low

  2. Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost…

    in Windows 10 Software and Apps

    Windows Windows successfully diagnosed a low virtual memory condition. Svchost using almost…: HelloI have around 27 PCs on a site that intermittently experience software crashes a few times a week each. My software is a unity standalone build. After further investigation, it seems that many of these crashes are caused by ‘System out of memory’ issues. Looking at the…

  3. Windows successfully diagnosed the condition of no virtual memory.

    in Windows 10 Gaming

    Windows successfully diagnosed the condition of no virtual memory.: Recently I’ve been having problems with firefox crashing, and today I found in the event viewer that Firefox supposedly ate all he virtual memory. Firefox used 3,525 gibibytes in total, yet the virtual memory is set at 4975 mebibytes minimum and 15925 mebibytes maximum. I’ve…

  4. Windows successfully diagnosed the condition of no virtual memory.

    in Windows 10 Software and Apps

    Windows successfully diagnosed the condition of no virtual memory.: Recently I’ve been having problems with firefox crashing, and today I found in the event viewer that Firefox supposedly ate all he virtual memory. Firefox used 3,525 gibibytes in total, yet the virtual memory is set at 4975 mebibytes minimum and 15925 mebibytes maximum. I’ve…

  5. Windows successfully diagnosed a low virtual memory condition? Browser keeps crashing.

    in Windows 10 BSOD Crashes and Debugging

    Windows successfully diagnosed a low virtual memory condition? Browser keeps crashing.: My chrome and any browser based app keeps crashing for some reason. I don’t think this should happened as I have 16 GB of RAM and Windows said it allocated 32GB of Paging file.Here’s the event log recently:»Windows successfully diagnosed a low virtual memory condition. The…

  6. Windows successfully diagnosed a low virtual memory condition.

    in Windows 10 Customization

    Windows successfully diagnosed a low virtual memory condition.: Hi all, I have got the issue log analysis restart PC caused by low virtual memory. It is described more in the picture below:It is caused by two abnormal applicationsWindows Explorer explorer.exe: 38.25GB – Very High Memory UsageWe were not able to find what causes this….

  7. Windows successfully diagnosed a low virtual memory condition ?

    in Windows 10 Virtualization

    Windows successfully diagnosed a low virtual memory condition ?: Teams kept crashing so I took a look at the event log and found this message just before it crashed.

    Any idea why Unarchiver.exe (which I assume was something to do with 7zip) is using so much virtual memory? that’s 2.47Gb

    I’ve uninstalled 7zip but I keep getting the same…

  8. Windows successfully diagnosed a low virtual memory condition ?

    in Windows 10 BSOD Crashes and Debugging

    Windows successfully diagnosed a low virtual memory condition ?: Teams kept crashing so I took a look at the event log and found this message just before it crashed.

    Any idea why Unarchiver.exe which I assume was something to do with 7zip is using so much virtual memory? that’s 2.47Gb

    I’ve uninstalled 7zip but I keep getting the same…

  9. Windows successfully diagnosed a low virtual memory condition ?

    in Windows 10 Support

    Windows successfully diagnosed a low virtual memory condition ?: Teams kept crashing so I took a look at the event log and found this message just before it crashed.

    Any idea why Unarchiver.exe (which I assume was something to do with 7zip) is using so much virtual memory? that’s 2.47Gb

    I’ve uninstalled 7zip but I keep getting the same…

  10. How to deal with low virtual memory conditions

    in Windows 10 BSOD Crashes and Debugging

    How to deal with low virtual memory conditions: I started having problems on my Windows 10 system about 2 weeks ago and find myself rebooting every few days because things are crashing. When I look in the event viewer I see a lot of repeats of warning messages that look like this:

    Windows successfully diagnosed a low…

Источник

Skip to content

While troubleshooting something I came across this blog today – Detecting Low Virtual Memory Conditions in Windows 2008 and R2.

Basically, since Windows 2008 there’s an inbuilt low memory detection system called RADAR (Resource Exhaustion Detection and Resolution – cool acronym!) that will log such events.

You can find them in the System logs from source Resource-Exhaustion-Detector. These logs give more details too on what’s using the most resources. Apart from that, there’s also logs under Application & Service Logs > Microsoft > Windows > Resource-Exhaustion-Detector > Operational.

An example message from the System logs looks like this:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: store.exe (6292) consumed 82729553920 bytes, Microsoft.Exchange.ServiceHost.exe (4224) consumed 784441344 bytes, and w3wp.exe (4828) consumed 754692096 bytes.

Clicking on the details tab and switching to XML view gives more details:

&lt;SystemCommitLimit&gt;94487166976&lt;/SystemCommitLimit&gt;

&lt;SystemCommitCharge&gt;94218813440&lt;/SystemCommitCharge&gt;

&lt;ProcessCommitCharge&gt;91936743424&lt;/ProcessCommitCharge&gt;

&lt;PagedPoolUsage&gt;348168192&lt;/PagedPoolUsage&gt;

&lt;PhysicalMemorySize&gt;51528912896&lt;/PhysicalMemorySize&gt;

&lt;PhysicalMemoryUsage&gt;50936864768&lt;/PhysicalMemoryUsage&gt;

&lt;NonPagedPoolUsage&gt;241033216&lt;/NonPagedPoolUsage&gt;

(All this and more info can be found in the link I point to – so please check it out).

I was curious on what these figures meant though. Here’s what I understand from this great blog post by Mark Russinovich.

  • Physical memory – we know.
  • Virtual memory – is physical memory plus the page file on disk.
  • The virtual memory is effectively what the OS can commit to any process. Meaning, guarantee that it can provide. So the system commit limit about is basically the virtual memory. (Well not entirely, as the OS needs some physical memory for itself too).
  • Commit charge – the amount of committed memory across all active processes. This can’t exceed the system commit limit of course.
  • When a process commits a region of virtual memory, the operating system guarantees that it can maintain all the data the process stores in the memory either in physical memory or on disk. Not all memory allocated to a process is of the committed type. Mainly private memory and pagefile-backed are of the committed type. The former can be found via tools like Process Explorer. The latter needs some during around using the handles.exe command with the -l switch.
  • The type of memory allocated to a process depends on the sort of request it makes?

Источник

Your system ran out of virtual memory

Introduction

When SmartGit crashed, your computer was low on virtual memory.

This usually happens due to two reasons:

  1. One of the programs on your computer is bugged, gradually eating all
    available memory.
  2. You don’t have enough RAM installed and run too many programs. This
    shouldn’t be the case if you have at least 16GB RAM.

Windows: Diagnosing with Event Log

This is the best and easiest way to diagnose.

  1. Start Windows Event Viewer application
    1. Go to
      Control Panel → System and Security → Administrative Tools
    2. Start Event Viewer from there.
  2. Expand Windows Logs → System on the left.«
  3. Search for Resource-Exhaustion-Detector events
    1. Press Ctrl+F to open search box.
    2. Enter Resource-Exhaustion-Detector
    3. Search
  4. Investigate

    1. Double-click found event to view details for it.

    2. It will say something like this:

      Windows successfully diagnosed a low virtual memory condition.
The following programs consumed the most virtual memory:
BuggedProgram.exe (11584) consumed 55.660.101.632 bytes
firefox.exe (5304) consumed 1.009.725.440 bytes.

    3. Look for anything suspicious
      Values above 4.000.000.000 bytes are already suspicious.
      Values above 16.000.000.000 bytes most likely mean that this
      program causes problems for you.

  5. If these steps didn’t help you, please send us a mail!

Note

If you found the program, please let us know! This lets us help other
users better.

Windows: Diagnosing with our script

To try to diagnose the problem, please download, extract all files and
run AnalyseMemoryUsage.cmd :
https://www.syntevo.com/downloads/troubleshoot/AnalyseMemoryUsage.cmd.zip

Wait until it completes (usually takes some 10 seconds), scroll the output
to the top and study it.

These are reasonable values for typical workflows:

  1. Check Available. If it’s only a few percent of Total, your system
    is probably going to run out of memory soon.
  2. If you’re already low on memory, check Usage breakdown.
  3. If the majority of memory is spent on running programs, continue to
    Programs breakdown section.
  4. If the majority of memory falls into Not explained category, check
    if you’re running virtual machines (VMWare, VirtualBox, Docker, WSL,
    etc). Otherwise, a screenshot of RAMMap (see below) will be needed to
    continue investigation.
  5. If unsure, please send script output to us and we’ll try to help.

Note

If you found the program, please let us know! This lets us help other
users better.

Windows: Diagnosing with RAMMap

SysInternals RAMMap
is an utility that shows some additional kernel memory stats.

In typical workflows, each of these values should be below 1GB:

  1. Page Table
  2. Paged Pool
  3. Nonpaged pool
  4. System PTE (except when you run virtual machines)
  5. Session private
  6. Driver Locked
  7. Kernel Stack

If any of these counters is significantly higher then 1GB, this likely
points to a problem. Diagnosing it further is different for every case.

Didn’t find the program to be blamed?

Please contact support, attaching outputs from AnalyseMemoryUsage.cmd
and RAMMap and we will try to help.

Источник

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Как заменить логотип windows 10 при загрузке
  • Очистка winsxs windows 7 dism
  • Windows удаленный рабочий стол передача файлов
  • Как включить программную виртуализацию windows 10
  • Virtualbox синий экран windows xp