*What steps will reproduce the problem?
1. I've created a gear object grouped from multiple primary objects
2. I've created a junction between the gear and a hinge object
3. I've copied the gear and moved it and rotate it in sketchup space
4. Hit play for the simulation to start
*What is the expected output? What do you see instead?
The application crashes every time!
*What version of the product are you using? On what operating system?
SketchUp 8.0.16846
SketchyPhysics 3.2 (Dec2)
Windows 7 x64 Sp1
*Please provide any additional information below.
I run the program in debugger and this is the culprit stack:
ChildEBP RetAddr Args to Child
01408c6c 76faf5c9 c0000374 76fe4268 01408cb0
ntdll32!RtlReportCriticalFailure+0x29
01408c7c 76faf6a9 00000002 77c6f93c 00000000 ntdll32!RtlpReportHeapFailure+0x21
01408cb0 76f5dff5 00000008 02af0000 08625830 ntdll32!RtlpLogHeapFailure+0xa1
01408ce0 74b698cd 02af0000 00000000 08625838 ntdll32!RtlFreeHeap+0x64
01408d2c 028ed128 08625838 01408d44 07e1104c msvcrt!free+0xcd
WARNING: Stack unwind information not available. Following frames may be wrong.
01408d38 07e1104c 08625838 01408efc 07e1fcfd msvcrt_ruby18!ruby_xfree+0x18
01408d44 07e1fcfd 08625838 01409144 0afca658 dl!dlfree+0xc
[...]
0140ae8c 028dda3a 0e7a1b70 0140bb3c 0140bf28
SketchUp!OGRSpatialReference::GetRoot+0x1ef63
00000000 00000000 00000000 00000000 00000000
msvcrt_ruby18!rb_with_disable_interrupt+0x119a
It seems that is crashes when it tries to free a block from heap. At a closer
look the address freed (08625838) does not belong to any heap segment. It
actualy belongs to 'NewtonServer3.dll' address (most likely it's a global
variable because the page access rights are READ & WRITE).
0:000:x86> !address 08625838
Usage: Image
Allocation Base: 085c0000
Base Address: 08622000
End Address: 08626000
Region Size: 00004000
Type: 01000000 MEM_IMAGE
State: 00001000 MEM_COMMIT
Protect: 00000004 PAGE_READWRITE
More info: lmv m NewtonServer3
More info: !lmi NewtonServer3
More info: ln 0x8625838
Original issue reported on code.google.com by mirce...@gmail.com on 24 Mar 2013 at 12:11
Original issue reported on code.google.com by
mirce...@gmail.comon 24 Mar 2013 at 12:11Attachments: