After puzzling for some weeks about why my Windows 10 (20H2) system was becoming unstable and showing random crashes I realied that it usually followed some time after using OBS (27.0.1). I have now investigated the various performance monitor metrics associated with memory, and can see quite clearly that OBS is consuming memory at a great rate, and then not freeing this when it exits. As I have (had!) a tendency to leave OBS running even after I finished a session, I at least now know why the system eventually became unstable and ran out of memory.
Specifically, the program shows a dramatic increase in the use of Committed Memory, and in the use of Paged Pool Bytes, both of which will cause problems (I speak as a computer professional in my day job). The attached log file does not reveal anything of particualr interest, but the chart (from perfmon) shows an increase in the percentage of committed memory used from about 20% to about 45% in just on three hours.
I have not investigated the impact of different configurations, but have found that the memory leakage starts immediately OBS is started. It is independent of whether the Virtual Camera is on or off.
It would be worthwhile doing some investigation to see if this is common to other users and if it is a problme that can be found in the source code.
I do note this post which appears to relate to possibly related issues.
Specifically, the program shows a dramatic increase in the use of Committed Memory, and in the use of Paged Pool Bytes, both of which will cause problems (I speak as a computer professional in my day job). The attached log file does not reveal anything of particualr interest, but the chart (from perfmon) shows an increase in the percentage of committed memory used from about 20% to about 45% in just on three hours.
I have not investigated the impact of different configurations, but have found that the memory leakage starts immediately OBS is started. It is independent of whether the Virtual Camera is on or off.
It would be worthwhile doing some investigation to see if this is common to other users and if it is a problme that can be found in the source code.
I do note this post which appears to relate to possibly related issues.
