Crashes in MacOS 10.5.8

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 18/03/2011 at 16:54, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   12 
Platform:      Mac OSX  ; 
Language(s) :     C++  ;

---------
My plugin builds are done on a Mac (Core2Duo, 4GB) running 10.6.6 using Xcode 3.2.1 (64-bit).  It seems to be that most of my crash reports from users on the Mac is when they are running Cinema 4D R 12 on MacOS 10.5.8.  The crashes go past my plugin into Cinema 4D calls.

I've double and redouble checked.  My project's configuration uses the 10.5 Base SDK, Deployment Target set to Mac OS X 10.5, Compiler Version is GCC 4.2, and Instruction Scheduling is PowerPC G5.

Could there be any other reason why there are no such crashes on 10.6 (64 or 32 bit) but continuous issues on 10.5.8?

Also, I would love a list of the XCode project settings for the cinema4dsdk as we all know that XCode *never* resets configuration settings (lmao).  This way I could avoid replicating the resets when I'm comparing against my project settings.

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 19/03/2011 at 02:05, xxxxxxxx wrote:

Originally posted by xxxxxxxx

<ADDRESS>
User Information:
Cinema 4D Version:   12 
Platform:     
Mac OSX  ; 
Language(s) :    
C++  ;

---------
</ADDRESS> My plugin builds are done on a Mac (Core2Duo, 4GB) running 10.6.6 using Xcode 3.2.1 (64-bit).  It seems to be that most of my crash reports from users on the Mac is when they are running Cinema 4D R 12 on MacOS 10.5.8.  The crashes go past my plugin into Cinema 4D calls.I've double and redouble checked.  My project's configuration uses the 10.5 Base SDK, Deployment Target set to Mac OS X 10.5, Compiler Version is GCC 4.2, and Instruction Scheduling is PowerPC G5.Could there be any other reason why there are no such crashes on 10.6 (64 or 32 bit) but continuous issues on 10.5.8?Also, I would love a list of the XCode project settings for the cinema4dsdk as we all know that XCode *never* resets configuration settings (lmao).  This way I could avoid replicating the resets when I'm comparing against my project settings.

Are you sure that this is r12? I can only find two r12 & OS X 10.5 releated crashes of you plugins in our DB; the other ones are on Windows or OS X 10.6.

Are you using your own bugreport system or how do you get these crash reports?

As far as I can see there are two general problems (not related to OS X 10.5) in your plugin:
- Trashed memory
- Usage of the zlib functions with invalid pointers

To my knowledge there is only one serious problem on OS X 10.5: a possible crash in the movie loader when accessing a MOV file - and that is a Apple bug (fixed in OS X 10.6).

Best regards,

Wilfried

P.S.: You might consider upgrading your XCode version, as I remember vague, that we had been hunting down a crash last year (when r12 was still in beta) that was caused by a compiler bug - and fixed in XCode 3.2.2

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 19/03/2011 at 23:41, xxxxxxxx wrote:

I requested the crash report from the user experience the crashes.  Here is the first part (of the Apple report) :

Process:         CINEMA 4D [31078]
Path:            /Applications/MAXON/CINEMA 4D R12/CINEMA 4D.app/Contents/MacOS/CINEMA 4D
Identifier:      net.maxon.cinema4d
Version:         12.0 (12.0)
Code Type:       X86-64 (Native)
Parent Process:  launchd [137]
 
Interval Since Last Report:          590 sec
Crashes Since Last Report:           2
Per-App Interval Since Last Report:  190 sec
Per-App Crashes Since Last Report:   1
 
Date/Time:       2011-03-18 23:06:25.656 +0100
OS Version:      Mac OS X 10.5.8 (9L31a)
Report Version:  6
Anonymous UUID:  D6CFE750-4543-45BA-9C98-D8A782404AC4
 
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000
Crashed Thread:  0
 
Thread 0 Crashed:
0   net.maxon.cinema4d              0x00000001003adfe1 SlotAllocator::Free(void* ) + 33
1   net.maxon.cinema4d              0x00000001000116c1 String::operator=(String const&) + 177
2   InterPoserPro.dylib                 0x000000011a610bed IPPLoader::ParseDoc() + 77
3   InterPoserPro.dylib                 0x000000011a62b755 IPPLoader::Parse(unsigned char) + 15541
4   InterPoserPro.dylib                 0x000000011a62da57 IPPLoader::Begin(BaseDocument*, Filename const&, Filename const&, unsigned int, int, int) + 2599
5   InterPoserPro.dylib                 0x000000011a57d474 IPPDialog::LoadScene(int) + 4532
6   InterPoserPro.dylib                 0x000000011a589817 IPPDialog::Command(int, BaseContainer const&) + 2231
7   InterPoserPro.dylib                 0x000000011a588ac0 IPPDialog::Message(BaseContainer const&, BaseContainer&) + 128
8   InterPoserPro.dylib                 0x000000011a725908 __ZL15CDialogCallBackP7CDialogP9CUserAreaP13BaseContainer + 264
9   net.maxon.cinema4d              0x00000001001bfb3b __ZL25C_special_bfparentmessageRP13CoffeeCDialogRK13BaseContainerP11CBaseDialog + 139
10  net.maxon.cinema4d             0x00000001001bfd11 CBaseDialog::BfParentMessage(BaseContainer const&) + 65
I'll check the code there to see if there is something not being checked properly.

Any more information on the 'Trashed memory'?

Not sure what you mean about zlib functions with invalid pointers.  I can check my code again but all pointers are checked (somewhere) before use.

Thanks for the advice!

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 20/03/2011 at 02:31, xxxxxxxx wrote:

Originally posted by xxxxxxxx

I requested the crash report from the user experience the crashes.

[...]

I'll check the code there to see if there is something not being checked properly.Any more information on the 'Trashed memory'?Not sure what you mean about zlib functions with invalid pointers.  I can check my code again but all pointers are checked (somewhere) before use.Thanks for the advice!

Well that is an example of a memory trasher. You're assigning a string in your parsing code and either that string is damaged or something nearby that memory area damaged the memory pointers (leading to a memory violation when memory management was touching that pointer).

The zlib problem looks like this (OS X 10.6 crash in this case) :

Call_Stack_Thread_0
    xtensions.dylib = inflate_fast
    xtensions.dylib = inflate
    xtensions.dylib = uncompress
    xtensions.dylib = IntUncompressData()
    InterPoserPro.dylib = __ZN7IPPBase14DeformGeometryEv + 0x139
    InterPoserPro.dylib = __ZN7IPPBase10DeformBoneEv + 0x4029
    InterPoserPro.dylib = __ZN7IPPBase12ModifyObjectEP10BaseObjectP12BaseDocumentS1_RK7LMatrixS6_diP10BaseThread + 0xfc1
    CINEMA 4D = PluginObject::GetModifiedObjects()
    CINEMA 4D = BaseObject::ModifyObject()
    CINEMA 4D = PreparePolyCache()
    CINEMA 4D = CalculateCaches()
    CINEMA 4D = SceneHookExecution::Execute()
    CINEMA 4D = PrepareScene()
    CINEMA 4D = ViewScheduler::Main()
    CINEMA 4D = CoreThreadSynchronous::Start()
    CINEMA 4D = CoreThreadState::StartSynchronous()

As far as I can see from the cpu registers attached to the crashlog, I think you've passed an invalid or damaged source pointer (it 's not NULL, but pointing to a random mem location) to the uncompress routine.

Best regards,

Wilfried