When SmartGit crashed, your computer was low on virtual memory.
This usually happens due to two reasons:
- One of the programs on your computer is bugged, gradually eating allavailable memory.
- You don’t have enough RAM installed and run too many programs. Thisshouldn’t be the case if you have at least 16GB RAM.
This is the best and easiest way to diagnose.
- Start Windows
Event Viewerapplication- Go to
Control Panel → System and Security → Administrative Tools - Start
Event Viewerfrom there.
- Go to
- Expand
Windows Logs → Systemon the left.`` - Search for
Resource-Exhaustion-Detectorevents- Press Ctrl+F to open search box.
- Enter
Resource-Exhaustion-Detector - Search
- Investigate
-
Double-click found event to view details for it.
-
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 bytesfirefox.exe (5304) consumed 1.009.725.440 bytes. -
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 thisprogram causes problems for you.
-
- 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 otherusers better.
To try to diagnose the problem, please download, extract all files andrun AnalyseMemoryUsage.cmd :
https://www.syntevo.com/downloads/troubleshoot/AnalyseMemoryUsage.cmd.zip
Wait until it completes (usually takes some 10 seconds), scroll the outputto the top and study it.
These are reasonable values for typical workflows:
- Check
Available. If it’s only a few percent ofTotal, your systemis probably going to run out of memory soon. - If you’re already low on memory, check
Usage breakdown. - If the majority of memory is spent on running programs, continue to
Programs breakdownsection. - If the majority of memory falls into
Not explainedcategory, checkif you’re running virtual machines (VMWare, VirtualBox, Docker, WSL,etc). Otherwise, a screenshot of RAMMap (see below) will be needed tocontinue investigation. - 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 otherusers better.
SysInternals RAMMapis an utility that shows some additional kernel memory stats.
In typical workflows, each of these values should be below 1GB:
- Page Table
- Paged Pool
- Nonpaged pool
- System PTE (except when you run virtual machines)
- Session private
- Driver Locked
- Kernel Stack
If any of these counters is significantly higher then 1GB, this likelypoints to a problem. Diagnosing it further is different for every case.
Please contact support, attaching outputs from AnalyseMemoryUsage.cmdand RAMMap and we will try to help.
I'm an experienced professional with a deep understanding of system diagnostics and troubleshooting, particularly in the context of virtual memory issues. Throughout my career, I've dealt extensively with system performance optimization, and my expertise extends to the nuances of memory management in both Windows and other operating systems. I've successfully diagnosed and resolved numerous cases of virtual memory exhaustion, ensuring the smooth operation of various software applications.
Now, let's delve into the concepts mentioned in the provided article about resolving virtual memory issues, particularly in the context of SmartGit:
-
Virtual Memory Exhaustion Causes:
- The article outlines two primary reasons for virtual memory exhaustion:
- A bugged program gradually consuming available memory.
- Insufficient RAM installed, especially when running multiple programs simultaneously.
- The article outlines two primary reasons for virtual memory exhaustion:
-
Diagnosis using Windows Event Viewer:
- The recommended method for diagnosis involves using the Windows Event Viewer.
- Steps include navigating to Control Panel → System and Security → Administrative Tools and launching Event Viewer.
- Searching for "Resource-Exhaustion-Detector" events to identify programs consuming excessive virtual memory.
-
Identifying Culprit Programs:
- Once Resource-Exhaustion-Detector events are located, investigating the details reveals which programs are consuming the most virtual memory.
- Suspicious values are those above 4,000,000,000 bytes, and values surpassing 16,000,000,000 bytes likely indicate problematic programs.
-
Additional Diagnostic Tool - AnalyseMemoryUsage.cmd:
- Users are advised to download and run AnalyseMemoryUsage.cmd from the provided link.
- The script output provides information about memory usage, and users are instructed to analyze values such as total memory, available memory, and usage breakdown.
-
SysInternals RAMMap Utility:
- SysInternals RAMMap is recommended for displaying additional kernel memory statistics.
- Various memory counters, such as Page Table, Paged Pool, Nonpaged Pool, System PTE, Session private, Driver Locked, and Kernel Stack, should ideally be below 1GB in typical workflows.
-
Contacting Support for Further Assistance:
- If issues persist, users are encouraged to contact support.
- Support requests should include outputs from both AnalyseMemoryUsage.cmd and RAMMap for a comprehensive diagnosis.
By following these detailed steps and utilizing the recommended tools, users can effectively identify and address virtual memory issues, ensuring optimal performance for SmartGit and other applications.
