Well; I was inaccurate in my previous post, as our dll is LAA, so I edited it. My point was that the exe is handling RAM allocation, and it is not giving us more than 2.8 GB for whatever reason.
It might have something to do with how BtS is running python natively, maybe 1.2 GB is reserved for python cache.
Also, I'm pretty sure this is correct: https://social.msdn.microsoft.com/F...e-of-large-address-aware-dll?forum=vclanguage
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Purpose of large address aware dll
Question: My application (EXE) is large address aware and it uses a DLL. This DLL dynamically allocates memory.
...
Interesting point is that non large address aware DLL was also able to dynamically allocate more than 2GB. So, what does large address aware flag signify for a DLL?
Answer: Nothing. Only the flag on the .exe matters.
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
So our dll is just a slave to the "dll within the exe" which is the file with the code that allocates RAM address space for the process, our dll doesn't matter in this regard.
It might have something to do with how BtS is running python natively, maybe 1.2 GB is reserved for python cache.
Also, I'm pretty sure this is correct: https://social.msdn.microsoft.com/F...e-of-large-address-aware-dll?forum=vclanguage
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Purpose of large address aware dll
Question: My application (EXE) is large address aware and it uses a DLL. This DLL dynamically allocates memory.
...
Interesting point is that non large address aware DLL was also able to dynamically allocate more than 2GB. So, what does large address aware flag signify for a DLL?
Answer: Nothing. Only the flag on the .exe matters.
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
So our dll is just a slave to the "dll within the exe" which is the file with the code that allocates RAM address space for the process, our dll doesn't matter in this regard.
Last edited: