-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.1
-
Component/s: None
-
Support Ticket IDs:
-
Epic Link:
In some scenarios, a crashing process can resulted in a corrupted cache file.
This strengthens the code by deleting the shared memory files on startup to guarantee a clean start.
This should already happen on other OSes.
Test using a shared memory file with am->global_size set incorrectly. When agent is down, put the files in the agent/logs directory
EXPECTED BEHAVIOUR
====================
Agent should always start cleanly and not crash on a request
ACTUAL BEHAVIOUR
==================
Agent crashes with a c0005 access violation in am_shm_lock+037
- is related to
-
OPENAM-9744 First process should delete and recreate shared memory files on windows
-
- Closed
-