Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashed by "Assertion failed" with packaged game ".exe" #33

Open
hikingyoung opened this issue Aug 24, 2021 · 1 comment
Open

Crashed by "Assertion failed" with packaged game ".exe" #33

hikingyoung opened this issue Aug 24, 2021 · 1 comment
Labels
awaiting replication bug Something isn't working

Comments

@hikingyoung
Copy link

After packaged, Every time I quit the game, either BP node "Quit Game" or console command "exit", the game will pop up an error window as below:
error

It's not caused by my code or any other logic because I test it with an almost "empty" ue4.26 project and crashed as well.
Map: default level. (from file ->new level ->Default)
Actor: Basic actor with a node component inside, the component runs a script that has only 1 line js code:

Console.log("hello world")

UE4 level outline

ue4 outline

My js script

my js script

Inside the BP actor

Runs Ok within UE4 editor

**After packaged, I run the .exe ** , then pop up a crash error windows as mentioned firstly above.
I think something caused Memory Leak, and I tried to figure it out.
After serveral days flew away (I first noticed this on August 3rd), now I know I can never do it.
Can you spare some time to help me ?
Hope your reply and any help will be highly appreciated.
Thank you again.
You Sincerely.

@getnamo getnamo added awaiting replication bug Something isn't working labels Aug 28, 2021
@Sakikonn
Copy link

Sakikonn commented Dec 21, 2021

@getnamo @hikingyoung
In NodeCmd.cpp

void FNodeCmd::StopMainScript()
{
	if (bIsMainRunning)
	{
		/*FCULambdaRunnable::RunLambdaOnBackGroundThread([this]
		{
			StopMainScriptSync();
		});*/

		StopMainScriptSync();
	}
}

I modified it,
It might be because of this asynchronous,
It doesn't crash now,
I don’t know what effect this modification will have
But now it will not crash after packaging,
I guess it may be caused by the callback.
My English is not good, I don’t know if this explanation is correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting replication bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants