Cinema crashed when selecting gradient

On 10/12/2016 at 09:49, xxxxxxxx wrote:

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

---------
I have a object with user data and in that user data a gradient.

Now, when I am in debugger mode (using MS Visual Express 2012 For Windows Desktop) and select the gradient, cinema 4d crashes with following information:
p:\c4d_perforce_work\release\16.0\modules\c4dplugin\source\src\richard\genesis\ge_container.h(211) : CRITICAL: Stop
CINEMA 4D.exe has triggered a breakpoint.

Note: When I start up cinema normally, it does not crash.

I use the debugger to debug a plugin, but even removing all most all code, it keeps crashing.

-Pim

On 11/12/2016 at 01:15, xxxxxxxx wrote:

I realize it is a very complex user data.
Are there restrictions to user data settings?
For example, is user data with the same name allowed?

-Pim

On 12/12/2016 at 07:13, xxxxxxxx wrote:

Originally posted by xxxxxxxx

<ADDRESS>
User Information:
Cinema 4D

Version:   r16 
Platform:   Windows  ;

Mac  ;  
Language(s) :    
C++  ;

---------
</ADDRESS> I have a object with user data and in that user data a gradient.
Now, when I am in debugger mode (using MS Visual Express 2012 For Windows Desktop) and select the gradient, cinema 4d crashes with following information:
p:\c4d_perforce_work\release\16.0\modules\c4dplugin\source\src\richard\genesis\ge_container.h(211) : CRITICAL: Stop
CINEMA 4D.exe has triggered a breakpoint.
Note: When I start up cinema normally, it does not crash.
I use the debugger to debug a plugin, but even removing all most all code, it keeps crashing.
-Pim

This ain't a crash but a CriticalStop (you can continue in the Debugger, if you want) designed to get the attention of a developer - and it 's a gentle reminder that you're accessing data in a BaseContainer in an improper way (e.g. having float data stored for that ID but trying to load it as integer).

I'd suggest to check your calling code...

Best regards,

Wilfried

On 12/12/2016 at 08:03, xxxxxxxx wrote:

Ok, thanks for the explanation.
I will double check!

-Pim

On 12/12/2016 at 08:17, xxxxxxxx wrote:

Ooopsy, didn't realize Wilfried already got into it.

Hi Pim,

what you are seeing there actually is not a crash. It's a CritcalStop() left in there by one of our developers. You should be able to press "Continue" in your debugger at that point.

In this special case it looks like there's some wrongly typed data in a BaseContainer (maybe you created user data via code and got a parameter type wrong?). Cinema wants to read an integer value from a container here, but the data stored seems to be of a different type. Maybe this already helps to find the issue?

Unfortunately I can't reproduce the behavior you described above by adding a gradient from the user interface. Can you give us a more detailed recipe to reproduce?

On 13/12/2016 at 05:05, xxxxxxxx wrote:

Thanks for the explanation and compliments for this feature.
Now I know it, debugging gets even simpler and easier.

I will check my expresso and if I have more questions, I will let you know.

-Pim