Greetings,
Today while working on my project, the editor began crashing (EXCEPTION_ACCESS_VIOLATION reading address 0x00000018) when attempting to spawn EnemyOrbs2 from Boss2:
This all began when I created a new map, and then when back to the old map which contained Boss2. At first I thought it was a corrupt uasset, but I no longer believe this to be the case. I deleted all of the assets that were causing the project to crash when opened, and reloaded earlier versions of them only to encounter the same problem. After a few hours of debugging, I narrowed it down to the Boss2 and EnemyOrbs2 assets. Specifically when Boss2 tries to spawn EnemyOrbs2 shown in the screenshot above.
Here are some of my debugging notes (from closing and reopening the editor over and over):
-Attempting to open Boss2 when “Spawn Actor EnemyOrbs2” node is connected results in a crash
-Removing the EnemyOrbs2 asset allows Boss2 to be opened
-Removing and then replacing EnemyOrbs2 allows both Boss2 and EnemyOrbs2 to be opened, but after closing and reopening the editor the error will occur again
-Removing the “Spawn Actor EnemyOrbs2” node allows both Boss2 and EnemyOrbs2 to be opened, closing and reopening the editor will not cause the problem to occur again
-Removing all code from EnemyOrbs2 does not fix the problem
-Creating a new blueprint with the same code from EnemyOrbs2 does not fix the problem
-Spawning other actors from the same node in Boss2 does not result in an error
-Spawning EnemyOrbs2 from a different blueprint does not result in an error
-Renaming events does not fix the error
-“Fix up redirections” does not fix the error
I also looked through the log files during all of this (albeit I’m not really sure what to be looking for) so here is one of them:
[Log File][2]
I kept seeing the “EXCEPTION_ACCESS_VIOLATION reading address 0x00000018” error, and after searching through other answers it would appear that using the “Spawn Actor” is accessing memory it shouldn’t whenever it attempts to spawn that asset. I don’t really know what happens behind the scenes when you go to open a blueprint, so I’m guessing whatever happens there is behind the issue I’m seeing.
If someone who has seen this before would be so kind as to enlighten me on how to fix this, I would be grateful.