Win7 64bit memory leaks

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

On 12/02/2010 at 09:06, xxxxxxxx wrote:

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

---------
Hi,

whenever I open up c4d and add an object (let´s say a cube) and then close c4d, the debug console shows these memory leaks:

btree_container <2363>
operatingsystem <3702>

The longer you work the more of these memory leaks appear after closing c4d. I was not sure if I should report this here or via the usual bug reporting form on the website.

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

On 03/02/2011 at 18:09, xxxxxxxx wrote:

I had the same problem! I didn't realize they were called memory leaks!

So have you read the 3 Week Diet review on the SkinnyExpress? You can Click Here if you haven't already read it.

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

On 07/02/2011 at 04:00, xxxxxxxx wrote:

Originally posted by xxxxxxxx

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

---------
</ADDRESS> Hi,whenever I open up c4d and add an object (let´s say a cube) and then close c4d, the debug console shows these memory leaks: btree_container <2363>operatingsystem <3702>The longer you work the more of these memory leaks appear after closing c4d. I was not sure if I should report this here or via the usual bug reporting form on the website.

Either your bugreport doesn't include all necessary steps (to reproduce the problem), or the memory leak is triggered by a 3rd party plugin.

I checked it with the current release (12.032) on Win7 - adding a cube and then quiting C4D - and there's no leak (using no 3rd party plugins).

Best regards,

Wilfried

P.S.:Katachi, you're ahead of time (Feb 12 says your post :-)

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

On 07/02/2011 at 04:46, xxxxxxxx wrote:

Hi Wilfried,

yes, it also says 2010 ;-) I assume it was still in 11.5, I also don't get any leaks in the current R12 release anymore.

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

On 07/02/2011 at 11:05, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Hi Wilfried,yes, it also says 2010 ;-) I assume it was still in 11.5, I also don't get any leaks in the current R12 release anymore.

:-) Looks like I need more sleep ...

Best regards,

Wilfried

On 20/06/2016 at 21:50, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Hi Wilfried,

yes, it also says 2010 ;-) I assume it was still in 11.5, I also don't get any leaks in the current R12 release anymore. So have you read the Burn The Fat Feed The Muscle review on fitnessbond? You can click here you haven't already read it.

Correct, no more memory leaks in the R12 version.

On 24/09/2016 at 09:03, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Originally posted by xxxxxxxx

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

---------
</ADDRESS> Hi,whenever I open up c4d and add an object (let´s say a cube) and then close c4d, the debug console shows these memory leaks: btree_container <2363>operatingsystem <3702>The longer you work the more of these memory leaks read this review appear after closing c4d. I was not sure if I should report this here or via the usual bug reporting form on the website.

Either your bugreport doesn't include all necessary steps (to reproduce the problem), or the memory leak is triggered by a 3rd party plugin.

I checked it with the current release (12.032) on Win7 - adding a cube and then quiting C4D - and there's no leak (using no 3rd party plugins).

Best regards,

Wilfried

P.S.:Katachi, you're ahead of time (Feb 12 says your post :-)

Well i know this post is too old but i was having the same issue, finaly i decided to upgrade my self to win10