After upgrading project to 4.14.X (currently 4.14.2) we got crashes when clicking PLAY in editor on most of levels (even simple test level with few objects).
Exception thrown at 0x00007FF88652291F (PhysX3PROFILE_x64.dll) in UE4Editor.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.
If there is a handler for this exception, the program may be safely continued.
callstack:
PhysX3PROFILE_x64.dll!physx::shdfnd::Array<unsigned int,physx::shdfnd::VirtualAllocator>::growAndPushBack(const unsigned int & a) Line 767 C++
PhysX3PROFILE_x64.dll!physx::Bp::SimpleAABBManager::updateAABBsAndBP(unsigned int numCpuTasks, physx::Cm::FlushPool & flushPool, physx::PxcScratchAllocator * scratchAllocator, bool hasContactDistanceUpdated, physx::PxBaseTask * continuation, physx::PxBaseTask * narrowPhaseUnlockTask) Line 1928 C++
PhysX3PROFILE_x64.dll!physx::Sc::Scene::broadPhase(physx::PxBaseTask * continuation) Line 2150 C++
PhysX3PROFILE_x64.dll!physx::Cm::Task::run() Line 59 C++
> UE4Editor-Engine.dll!TGraphTask<FPhysXTask<0> >::ExecuteTask(TArray<FBaseGraphTask *,FDefaultAllocator> & NewTasks, ENamedThreads::Type CurrentThread) Line 868 C++
UE4Editor-Core.dll!FTaskThreadAnyThread::ProcessTasks() Line 1255 C++
UE4Editor-Core.dll!FTaskThreadAnyThread::ProcessTasksUntilQuit(int QueueIndex) Line 1149 C++
UE4Editor-Core.dll!FTaskThreadBase::Run() Line 621 C++
UE4Editor-Core.dll!FRunnableThreadWin::Run() Line 74 C++
UE4Editor-Core.dll!FRunnableThreadWin::GuardedRun() Line 23 C++
[External Code]
This seems to be related to PhysX and could be related to the upgrade to PhysX 3.2 with engine version 4.14. What version of the engine was your project on prior to upgrading? Are you doing anything with physics in these levels that crash?
Additionally, I would recommend sticking to our released engine versions. When syncing to the engine in Github, please sync to Release or one of the Tags, such the 4.14.1 tag. 4.14.2 (which I’m assuming you got from syncing to the “4.14” branch) has not yet been released and any changes in the 4.14 branch past the 4.14.1 release would be considered to be less stable and more prone to errors.
Hello, thanks for reply.
Previously we used 4.13.1 and everything was fine.
Currently I synced to official 4.14.1-release tag and we got the same crash.
I dont think we do much with physics on craching levels - it occurs also on test levels, where we for example got explosive barrel and we may shot it with weapon spawning projectiles.
But this crash also happen when I do simple test: create new level, put player start on it, and just press play in editor.
Thank you for that information. That’s interesting that it’s specific to this project, yet still occurs with a new map. In your Project Settings, do you have a custom Default GameMode set or any custom values set for the fields under Selected GameMode in Project > Maps & Modes > Default Modes? I’m wondering if it could be your default pawn that is causing this issue, since you’re able to set a player start in the level and hit play to cause it to crash.
If any of these fields are set, can you try setting them to the defaults to see if the crash still persists?
You were right, changing that to defaults, made that there were no crashes, that pointed me to solution. Something must have beed changed in order of stuff initialization in 4.14, becouse our mechanics connected with game instance were now not properly initialized. I moved it somewhere else and now seems to work. So this topic is closed.
Thanks for your help.