[PD] Gem separator pb

[vincent rioux]

hi Chris,
that was it!
thanks for the tip.
i will try on linux with Gem cvs when i find time.
you can test this pb with the attached patch (simplified).
after creating the Gem window, simply loading a video file does produce 
the memory leak error.
i was may be wrong in setting the "separator" object just after the 
"gemhead" object.

best,
vincent

chris clepper wrote:

>On 1/30/06, vincent rioux <vincent.rioux at no-log.org> wrote:
> > I have another pb with Gem and separator object on osx (pd 39.2, Gem
>  
>
>>from latest Hans'installer).
>>with several pix_film and separators, once i load a movie i get this output:
>>separator : state->numTexCoords 4 != m_state.numTexCoords 0
>>...
>>separator : state->numTexCoords 4 != m_state.numTexCoords 0
>>    
>>
>
>This means you are leaking memory using the separator object.  See if
>moving them after pix_texture gets rid of the message.
>
>Also, I have no idea where Hans gets GEM for his installers, so post
>the patch or something representitive and I will see if the current
>CVS version does it.
>
>_______________________________________________
>PD-list at iem.at mailing list
>UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
>
>  
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20060131/42f92bfd/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: test-Gem-separator-memory-leak.pd
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20060131/42f92bfd/attachment.txt>