On Sun, 2006-03-19 at 20:18 +0100, Petter Reinholdtsen wrote: > As reported in bug #348504, classpath can sometimes deadlock when > image drawing is done in parallel with other graphics operations. > This was discovered when testing worldwind2d with cacao. > > Mark Wielaard had a look at this problem and proposed a patch that is > available from > <URL:http://article.gmane.org/gmane.comp.java.classpath.patches/7660>. > > Please apply this to the next upload of classpath. I tested this > patch, and it fixed the deadlock.
That patch is now committed to GNU Classpath cvs. But since key events aren't fully working yet you will want to have a scroll wheel mouse and also the following patch installed: http://article.gmane.org/gmane.comp.java.classpath.patches/7653 > Now cacao get as far as drawing some of the window before reporting > this error. Had to use '-Xmx200M' to avoid OOM exceptions. I used -Xmx750M :) > WW2D 0.99.87 by Vitaliy Pronkin <[EMAIL PROTECTED]> starting... > The program '.' received an X Window System error. > This probably reflects a bug in the program. > The error was 'GLXBadRenderRequest'. > (Details: serial 266 error_code 164 request_code 145 minor_code 1) > (Note to programmers: normally, X errors are reported > asynchronously; that is, you will receive the error a while after > causing it. To debug your program, run it with the --sync > command line option to change this behavior. You can then get a > meaningful backtrace from your debugger if you break on the > gdk_x_error() function.) > > This error might be related to the fact that I run ww2d across an ssh > X tunnel. That is worrying. That might mean that we have a timing related drawing/locking bug where multiple thread do try to access X at the same time. Or there is some bug which makes GLX detection go bonkers when done over the ssh wire.
signature.asc
Description: This is a digitally signed message part
