4.10 Access violation running "set " works in same project in 4.9.x

Development Programming & Scripting
1

I am running into a bug where if i call
"set "
From the console, to a c++ class, i get a crash with an access violation.
It happens on anything i call.
This is a feature that works fine in 4.9.2, but after upgrading to 4.10 it no longer works.

Am i doing something stupid or is this a bug?

2

Hello gozu,

In the event of a crash, please post the callstack that you receive as it can point us toward where the crash is occurring in code and it also allows us to look up previous/other instances of the crash. Can you please provide this for me? Also, when you say you’re calling “set” from the console, what are you calling set on exactly?

3

To make things easier i have replicated the problem for you inside the ShooterGameExample, and clicked on the “send” to send the crash dump. I hope this is helpful!

MachineId:AABB0B424083144D238FD9B15678F7D1
EpicAccountId:cae8145aa03e444783516a8798192691

No minidump found for this crash.

4

This example was running
“set ShooterCharacter RunningSpeedModifier 2”

just as a random example.

5

More info here. In order to get a callstack i started it from VS using the “Local Windows Debuger” option, and i dont get the crash.
However, close that, go back into the editor, click on “launch” repeat the same process, and i get the crash.

6

To confirm, are you only getting the crash when playing in Standalone or while launched? Does it ever occur while in PIE and does it ever actually crash the editor itself or just the game instance?

7

This is something you can only do in Standalone, the functionality gets disabled in PIE.

note: it also happens in the patch that just came out today.

thanks!

8

Thank you for confirming that, I’ve not previously used this console command so I wasn’t sure. I’ve placed a bug into our system under the number UE-24292. I’ll be sure to update you when any updates are made to this issue to let you know when it has been marked as fixed.

Have a nice day!

9

A fix has gone in for this issue now and was just put into the Master branch. This means that it is now available on Github if you would like to apply the changes to your source built engine if you’re using it. You can find the fix here: .com/EpicGames/UnrealEngine/commit/22e82ebeb53d8c32d99fd983e236c4bfe6fc4c98

Please be aware that this fix is lumped in with multiple others so be sure to read through the description to ensure that you want to use this fix.