From d11708e398c2f6377d9eac2b1f7248c62faab569 Mon Sep 17 00:00:00 2001 From: Sheikh Dawood Abdul Ajees Date: Tue, 25 Apr 2017 16:02:08 -0500 Subject: PhysX 3.4, APEX 1.4 patch release @22017166 --- PhysX_3.4/Source/LowLevel/software/src/PxsContext.cpp | 18 ------------------ 1 file changed, 18 deletions(-) (limited to 'PhysX_3.4/Source/LowLevel/software/src/PxsContext.cpp') diff --git a/PhysX_3.4/Source/LowLevel/software/src/PxsContext.cpp b/PhysX_3.4/Source/LowLevel/software/src/PxsContext.cpp index d9bcc3d1..6735b3aa 100644 --- a/PhysX_3.4/Source/LowLevel/software/src/PxsContext.cpp +++ b/PhysX_3.4/Source/LowLevel/software/src/PxsContext.cpp @@ -63,24 +63,6 @@ using namespace physx::shdfnd; #define PXS_BODYSHAPE_SLABSIZE 1024 #define PXS_MAX_BODYSHAPE_SLABS 16 - -void PxsCMUpdateTask::release() -{ - // We used to do Task::release(); here before fixing DE1106 (xbox pure virtual crash) - // Release in turn causes the dependent tasks to start running - // The problem was that between the time release was called and by the time we got to the destructor - // The task chain would get all the way to scene finalization code which would reset the allocation pool - // And a new task would get allocated at the same address, then we would invoke the destructor on that freshly created task - // This could potentially cause any number of other problems, it is suprising that it only manifested itself - // as a pure virtual crash - PxBaseTask* saveContinuation = mCont; - this->~PxsCMUpdateTask(); - if (saveContinuation) - saveContinuation->removeReference(); -} - - - PxsContext::PxsContext(const PxSceneDesc& desc, PxTaskManager* taskManager, Cm::FlushPool& taskPool, PxU64 contextID) : mNpThreadContextPool (this), mContactManagerPool ("mContactManagerPool", this, 256, 8192), -- cgit v1.2.3