Project

General

Profile

Bug #1220

PhysX 0.13 Segmentation Faults with Standalone

Added by Sean Mondesire about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
11/12/2015
Due date:
% Done:

0%


Description

When running PhysX v 0.13 Standalone with the ballPit.oar on Ubuntu, OpenSim generates the below stack trace and error when the following commands are executed:
ptp Set Ball Count 10000
ptp Spawn Balls

./../../PhysX/src/NpScene.cpp (218) : invalid operation : PxScene::release(): Scene is still being simulated! PxScene::fetchResults() is called implicitly.

Stacktrace:

at <unknown> <0xffffffff>
at (wrapper managed-to-native) OpenSim.Region.Physics.PhysXPlugin.PxAPIManager/PxAPI.releaseScene () <0xffffffff>
at OpenSim.Region.Physics.PhysXPlugin.PxAPIManager.DisposeScene () <0x0000b>
at OpenSim.Region.Physics.PhysXPlugin.PxScene.Dispose () <0x0003b>
at OpenSim.Region.Framework.Scenes.Scene.Close () <0x003c3>
at OpenSim.Region.Framework.Scenes.SceneManager.Close () <0x000a8>
at OpenSim.OpenSimBase.ShutdownSpecific () <0x00143>
at OpenSim.OpenSim.ShutdownSpecific () <0x0003b>
at OpenSim.Framework.Servers.ServerBase.Shutdown () <0x00024>
at OpenSim.Framework.Servers.ServerBase.<RegisterCommonCommands>m__2 (string,string[]) <0x00013>
at OpenSim.Framework.Console.Commands.Resolve (string[]) <0x000cb>
at OpenSim.Framework.Console.RemoteConsole.ReadLine (string,bool,bool) <0x00225>
at OpenSim.Framework.Console.CommandConsole.Prompt () <0x00046>
at OpenSim.Application.Main (string[]) <0x00a52>
at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

mono() [0x4b5bc0]
mono() [0x50ecfb]
mono() [0x424063]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10) [0x7f430559ad10]
/home/sean/src/opensimPhysX0.13/bin/lib64/libPhysX3_x64.so(+0x1a8b24) [0x7f4284b5eb24]

Debug info from gdb:

16:42:21 - [PHYSX SCENE], Collider ID not found in object list, ID = 3047144572

Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application. =================================================================

History

#1 Updated by Glenn Martin about 3 years ago

  • Status changed from New to Fixed

#2 Updated by Glenn Martin about 3 years ago

  • Status changed from Fixed to Closed

Also available in: Atom PDF