CureCure / bulletsharp

Automatically exported from code.google.com/p/bulletsharp
0 stars 0 forks source link

AccessViolationException on NearCallback event #69

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. uncomment the last line with the NearCallback. The MyNearCallback exists and 
it's empty
 Dispatcher = new CollisionDispatcher(CollisionConf);
 Broadphase = new DbvtBroadphase();
 World = new DiscreteDynamicsWorld(Dispatcher, Broadphase, new SequentialImpulseConstraintSolver(), CollisionConf);
 //Dispatcher.NearCallback += MyNearCallback;
2. run it and see it :)

What is the expected output? What do you see instead?
System.AccessViolationException was unhandled
  HResult=-2147467261
  Message=Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
  Source=BulletSharp
  StackTrace:
       bei BulletSharp.Dispatcher.!Dispatcher()
       bei BulletSharp.Dispatcher.Dispose(Boolean )
       bei BulletSharp.Dispatcher.Finalize()
  InnerException: 

What version of the product are you using? On what operating system?
Bulletsharp r638
VisualStudio 2012
Windows 7

Original issue reported on code.google.com by jspr...@gmail.com on 19 Jun 2014 at 3:04

GoogleCodeExporter commented 9 years ago
you see the exception on the second collision. but if you debug it, sometimes 
it' works fine.

Original comment by jspr...@gmail.com on 20 Jun 2014 at 6:15

GoogleCodeExporter commented 9 years ago
Confirmed. There's some dumb code there that doesn't keep references properly. 
The dispatcher shouldn't get disposed.

Thanks for the report!

Original comment by andres.traks on 20 Jun 2014 at 9:15

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r642.

Original comment by andres.traks on 21 Jun 2014 at 5:04