Runtime Error: Heap Corruption Detected (0xC0000374) #1
Description
!!! Please be aware that this Error occurs with our Test Application. If you use your own Application, the error might disappear. !!!
Our program is encountering a critical runtime error and crashing. The exit code -1073740940 (0xC0000374) indicates a Heap Corruption error, which is typically a result of incorrect dynamic memory operations.
Potential causes include:
Double deletion of memory: This happens when we attempt to delete memory that has already been deleted. Each allocated memory space should only be deleted once.
Accessing deleted memory:
This occurs when we try to access or use memory that has already been released/deleted.
Buffer overflow:
When dynamic memory bounds are exceeded, for instance, through an off-by-one error or incorrect calculation, causing memory overwrite which may corrupt other data structures or instructions in memory.
Race condition in multithreading:
If the program has multiple threads and the program doesn't prevent them properly, one thread might be accessing memory while another is deleting the same memory.
We need to identify the root of this issue and correct our memory management, so that each operation respects the rules and constraints of dynamic memory.
Requesting further investigation on this issue to avoid future crashes caused by this heap corruption error.
Expected Results:
The program runs without encountering the heap corruption error, ensuring smooth execution and reliable performance.
Actual Results:
The program is crashing due to a heap corruption error.
Environment:
Windows 11, 64-bit, using CLion 2024.1.4 with C++17.
The actual Issue Tracking is done via YouTrack