Posted by
Sven Gothel on
Dec 07, 2010; 12:34am
URL: https://forum.jogamp.org/re-NEWT-Threading-Overview-tp1991718p2030906.html
On Monday, December 06, 2010 12:29:39 BrickFarmer [via jogamp] wrote:
>
> The nabble email link failed for me, so anyway:
>
> I put the newt demo stuff on hold due to the OSX issues we discussed (i only have osx to work with). Also I need to investigate acquiring a pgp key. Is there no way to use a single account for all these tools? It seems like the login for the forum, bugzilla, wiki and probably git are all different?
>
> Currently I'm investigating the issue around single fpsAnimator with multiple runtime add/remove drawable calls. I'm working with b220, is there some way with GIT to get the matching source code for b220? or a matching zip file I can use in eclipse. I don't see any git tags/labels for doing this. I'm happy to investigate this myself, but I'm a total newbie with git...
>
> The errors I see are timeouts probably due to some lock contention:
>
> java.lang.RuntimeException: Waited 5000ms for: Thread[Timer-0,5,main] - Thread[AWT-EventQueue-0,6,main], with recursionCount 0, lock: com.jogamp.common.util.locks.RecursiveLock@7a0ec850, qsz 0
> at com.jogamp.common.util.locks.RecursiveLock.lock(RecursiveLock.java:125)
> at com.jogamp.opengl.util.AnimatorBase.remove(AnimatorBase.java:96)
even though I would always test with the latest, however, let's make this exercise with JOGL b220:
http://jogamp.org/deployment/archive/master/gluegen_207-jogl_220-jocl_200/jogl.artifact.propertiesgluegen.build.number=207
gluegen.build.id=2010-11-17_14-03-39
gluegen.build.branch=master
gluegen.build.commit=8c6de21bc52b825788fc6290e0dbb50e6707d31c
jogl.build.number=220
jogl.build.id=2010-11-17_14-11-15
jogl.build.branch=master
jogl.build.commit=29e3b223eae9f5775d1dd34f2aaeeb3db6d9233c
this gives you the git sha1 values which you can use to pull source code,
event as a zip download on github.
You just add the sha1 to
https://github.com/sgothel/jogl/commit/ie:
https://github.com/sgothel/jogl/commit/29e3b223eae9f5775d1dd34f2aaeeb3db6d9233cthen you click on 'Downloads' .. and you are good to go.
Sure, you can always reset your branch to any sha1 when using git.
We offer tags for rc's .. see v2.0-rc1.
If you like to share your bug investigation a small test case would be awesome,
then we could review and/or fix it in cooperation.
Cheers, Sven