OutOfMemory after update KB4534273

%3CLINGO-SUB%20id%3D%22lingo-sub-1122823%22%20slang%3D%22en-US%22%3EOutOfMemory%20after%20update%20KB4534273%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1122823%22%20slang%3D%22en-US%22%3E%3CP%3EWindowsServer%202019%2C%20Hyper-V%20instances%3A%201%20application%20server%2C%204%20rdhs%20servers.%20Database%20and%20related%20server%20run%20on%20application%20server%2C%20applications%20run%20by%20users%20run%20in%20remote%20sessions.%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20application%20update%20has%20been%20done%20on%20DEc.%2024th%20last%20year.%20No%20issues%2C%20all%20worked%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20Wednesday%20evening%2C%20this%20update%20(and%20some%20others%2C%20I%20don't%20have%20th%20whole%20list)%20is%20installed%20on%20all%20servers%20(physical%20and%20virtual).%20No%20problems%20on%20Thursday%20but%20since%20Friday%2C%20processes%20crash%20%3CSPAN%3Eafter%20some%20time%3A%20%3C%2FSPAN%3Eon%20either%20OutOfMemory%20or%20access%20violtation%20due%20to%20failure%20of%20creating%20objects%20(result%20is%20null%20on%20reference)%20on%20any%20location%20in%20the%20program%20after%20requesting%20memory%3C%2FP%3E%3CP%3ENo%20changes%20in%20application%20and%20database%20server%20(certain)%20or%20configuration%20(assumed).%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20assume%20this%20update%20since%20it%20also%20contained%20an%20update%20for%20Windows%20Virtualization.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ECould%20anyone%20give%20a%20hint%20what%20could%20cause%20these%20sudden%20occurring%20OutOfMemory%20messages%2C%20based%20on%20the%20Windows%20update%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1122823%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1122869%22%20slang%3D%22en-US%22%3ERe%3A%20OutOfMemory%20after%20update%20KB4534273%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1122869%22%20slang%3D%22en-US%22%3E%3CP%3EMight%20try%20removing%20the%20update%20as%20a%20test.%20I'd%20also%20engage%20the%20application%20developer%20for%20help%20debugging%20the%20process.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1171394%22%20slang%3D%22en-US%22%3ERe%3A%20OutOfMemory%20after%20update%20KB4534273%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1171394%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20not%20work%2C%20reversed%20to%20state%20before%20update%20by%20restroring%20backup.%20That%20improved%20matters%2C%20even%20better%20after%20moving%20back%20to%20WindowsWerver2016.%20No%20more%20memory%20issues%20but%20still%20quite%20slow%20-%20which%20seems%20to%20be%20a%20matter%20of%20configuration%20(WAY%20to%20little%20memory%20configured%20for%20each%20VM%20given%20the%20number%20of%20users%20on%20it).%20The%20issue%20with%20WindowsServer2019%20seems%20to%20be%20related%20to%20this%20(bad)%20configuration%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConsider%20problem%20'solved'%20-%20we%20now%20know%20the%20cause%20of%20problems%3A%20badly%20configured%20system%2C%20which%20became%20worse%20after%20this%20update%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

WindowsServer 2019, Hyper-V instances: 1 application server, 4 rdhs servers. Database and related server run on application server, applications run by users run in remote sessions. 

Last application update has been done on DEc. 24th last year. No issues, all worked fine.

 

Last Wednesday evening, this update (and some others, I don't have th whole list) is installed on all servers (physical and virtual). No problems on Thursday but since Friday, processes crash after some time: on either OutOfMemory or access violtation due to failure of creating objects (result is null on reference) on any location in the program after requesting memory

No changes in application and database server (certain) or configuration (assumed).

I assume this update since it also contained an update for Windows Virtualization.

Could anyone give a hint what could cause these sudden occurring OutOfMemory messages, based on the Windows update?

 

2 Replies

Might try removing the update as a test. I'd also engage the application developer for help debugging the process.

 

 

Did not work, reversed to state before update by restroring backup. That improved matters, even better after moving back to WindowsWerver2016. No more memory issues but still quite slow - which seems to be a matter of configuration (WAY to little memory configured for each VM given the number of users on it). The issue with WindowsServer2019 seems to be related to this (bad) configuration as well.

 

Consider problem 'solved' - we now know the cause of problems: badly configured system, which became worse after this update