Subject: Re: [PD] GEM on PIII memory problem?<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
To: <a href="mailto:pd-list@iem.at">pd-list@iem.at</a><br>
Message-ID: <<a href="mailto:4F1442F1.70606@iem.at">4F1442F1.70606@iem.at</a>><br>
Content-Type: text/plain; charset="iso-8859-15"<br>
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
On <a href="tel:2012-01-16%2015" value="+12012011615">2012-01-16 15</a>:51, rolf meesters wrote:<br>
><br>
> and now every time at a change in the rendering:<br>
> GL: invalid operation<br>
<br>
is that with the intel gfx card?<br>
</blockquote><div><br>the PIII has onboard video<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">could it be a dupe of [1]?<br></blockquote>
<div> </div><div>not as far as i can see. (i use fresh copies)<br>i suspect [1] has something to do with using the pd open or close 'message' with a non-existing file.<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
or what does "every time at a change in the rendering" mean exactly?<br>
<br></blockquote><div><br>every time the content of the GEM-window should change<br><br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
try to find the object that actually causes the error.<br>
you can use a [GEMglReportError] that will output a warning if an error<br>
was raised since the last time any instance of [GEMglReportError] was<br>
called (the error state is also reset inside [gemwin] during each<br>
render-cycle..which is what causes the message to appear)<br>
<br></blockquote><div><br>it's not clear to me how to use this object, there's no help.<br>connecting the inlet with a loadbang causes Pd/GEM to quit immediately.<br>leaving the object by itself, with a print on the first outlet, gives nothing.<br>
<br>i tried to use more then 16 k for the VideoRam: this also causes Pd/GEM to quit at rendering the first picture.<br><br></div></div>just now i found in the system message.log after the crash:<br> pdextended[1702]: segfault at 0 ip (null) sp bfcc1acc error 4 in libpulse.so.0.12.2[110000+40000]<br>
<br>doing it again:<br><br>pdextended[2045]: segfault at 0 ip (null) sp bfb87f3c error 4 in libasound.so.2.0.0[110000+c3000]<br><br>going back to the default VideoRam (= no changes made by me)<br><br>pdextended[1431]: segfault at 0 ip (null) sp bfe1aecc error 4 in libICE.so.6.3.0[110000+15000]<br>
<br>should i make a bug report on this? (i'm on Pd-ext 42.5 with GEM 92.3)<br><br>rolf<br><br>