[PD] GEM on PIII memory problem?
rolfmeesters at gmail.com
Mon Jan 16 18:06:40 CET 2012
Subject: Re: [PD] GEM on PIII memory problem?
> To: pd-list at iem.at
> Message-ID: <4F1442F1.70606 at iem.at>
> Content-Type: text/plain; charset="iso-8859-15"
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 2012-01-16 15:51, rolf meesters wrote:
> > and now every time at a change in the rendering:
> > GL: invalid operation
> is that with the intel gfx card?
the PIII has onboard video
> could it be a dupe of ?
not as far as i can see. (i use fresh copies)
i suspect  has something to do with using the pd open or close 'message'
with a non-existing file.
or what does "every time at a change in the rendering" mean exactly?
every time the content of the GEM-window should change
> try to find the object that actually causes the error.
> you can use a [GEMglReportError] that will output a warning if an error
> was raised since the last time any instance of [GEMglReportError] was
> called (the error state is also reset inside [gemwin] during each
> render-cycle..which is what causes the message to appear)
it's not clear to me how to use this object, there's no help.
connecting the inlet with a loadbang causes Pd/GEM to quit immediately.
leaving the object by itself, with a print on the first outlet, gives
i tried to use more then 16 k for the VideoRam: this also causes Pd/GEM to
quit at rendering the first picture.
just now i found in the system message.log after the crash:
pdextended: segfault at 0 ip (null) sp bfcc1acc error 4 in
doing it again:
pdextended: segfault at 0 ip (null) sp bfb87f3c error 4 in
going back to the default VideoRam (= no changes made by me)
pdextended: segfault at 0 ip (null) sp bfe1aecc error 4 in
should i make a bug report on this? (i'm on Pd-ext 42.5 with GEM 92.3)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list