ARKit/SceneKit physics engine crash

Question

Junjie Wang OP

Created Mar ’19

Replies 2

Boosts 1

Views 1.5k

Participants 3

My ARKit/SceneKit app crashes inside physics engine for a long time. I tried a lot to analyze it but nothing got.

Any one having experiences about crash of SceneKit physics engine? Thanks!

Signal:

SIGSEGV

SEGV_ACCERR

Logs:

SceneKit btDbvtBroadphase::setAabb(btBroadphaseProxy*, btVector3 const&, btVector3 const&, btDispatcher*) + 52
SceneKit btCollisionWorld::updateSingleAabb(btCollisionObject*) + 296
SceneKit btCollisionWorld::updateSingleAabb(btCollisionObject*) + 296
SceneKit btCollisionWorld::updateAabbs() + 56
SceneKit btCollisionWorld::performDiscreteCollisionDetection() + 36
SceneKit btDiscreteDynamicsWorld::internalSingleStepSimulation(float) + 120
SceneKit btDiscreteDynamicsWorld::stepSimulation(float, int, float) + 276
SceneKit -[SCNPhysicsWorld _step:] + 176
SceneKit -[SCNRenderer _update:] + 1156
SceneKit -[SCNRenderer _drawSceneWithNewRenderer:] + 248
SceneKit -[SCNRenderer _drawScene:] + 68
SceneKit -[SCNRenderer _drawAtTime:] + 768
SceneKit -[SCNView _drawAtTime:] + 488
SceneKit ___69-[NSObject(SCN_DisplayLinkExtensions) SCN_setupDisplayLinkWithQueue:]_block_invoke + 56
SceneKit ___36-[SCNDisplayLink _callbackWithTime:]_block_invoke + 80
libdispatch.dylib __dispatch_client_callout + 16
libdispatch.dylib __dispatch_lane_barrier_sync_invoke_and_complete + 56
SceneKit -[SCNDisplayLink _callbackWithTime:] + 268
QuartzCore CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 828
IOKit IODispatchCalloutFromCFMessage + 488
CoreFoundation ___CFMachPortPerform + 188
CoreFoundation ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 56
CoreFoundation ___CFRunLoopDoSource1 + 440
CoreFoundation ___CFRunLoopRun + 2140
CoreFoundation CFRunLoopRunSpecific + 436
Foundation -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 300
SceneKit ___49-[SCNView(SCNDisplayLink) _initializeDisplayLink]_block_invoke + 432
SceneKit ___SCNRenderThread_start__ + 72
libsystem_pthread.dylib __pthread_body + 128
libsystem_pthread.dylib _pthread_start + 48

Boost

Answer 1

Claude31 OP

Apr ’19

Crash is a segment violation.

The crash is caused bei

SIGSEGV

. This means the app is trying to send a message to an object that is invalid. This means you have at least one memory problem in your app (somewhere).

Have a look here for help for diagnostics

https://stackoverflow.com/questions/20244029/sigsegv-segv-accerr-error-no-method-from-app-referenced

use the

Analyze

feature of Xcode and fix all warnings it shows and also try running your app with

Enable Zombie Objects

set.

0

Answer 2

haozes OP

Sep ’22

Have the same issue, have you fixed?

0