On Tuesday, November 16, 2010 04:41:27 Aron [via jogamp] wrote:
>
> I'm switching builds back and forth in an effort to quash bugs. When I
> switched from build 209 to build 216, suddenly I get an exception calling
> drawable.getGL().getGL2(), saying it's not a GL2 profile.
>
> In build 209, the first time I call FBObject.init(gl), it says
> Framebuffer 1 is incomplete: status = 0xffffffff : NOT A FBO
> but if I simply call it again, it succeeds and works. Inserting a DebugGL2
> object lets me see that glBindFramebuffer is reporting out-of-memory that
> first time.
> Unfortunately, I'm seeing the out-of-memory error some other places, like
> when creating a vertex buffer object.
Awesome, thank you for your report.
Yes, I changed the memory mapping methodology a bit,
and as it seems, it's not stable yet.
I will add a junit test for this later on to show the bug and fix it.
>
> Anybody seeing something similar? Suggestions on which (windows) build might
> not have these issues?
As I said, I guess it's in the generic java code I changed ..
BTW ..
here is the proper way to make a proper report, using the internal build versioning:
http://jogamp.org/wiki/index.php/Jogamp_Versioning_and_Releases#Runtime_Version_Check http://jogamp.org/wiki/index.php/Jogl_FAQ#Runtime_Version_Check http://jogamp.org/wiki/index.php/Jogl_FAQ#Bugreports_.26_Testingyou see, it's simple and provides us with all the available information
about the build _and_ your running platform.
Thank you.
~Sven
--
health & wealth
mailto:
[hidden email] ;
http://jausoft.comland : +49 (471) 4707742 ; cell: +49 (151) 28145941
Timezone CET: PST+9, EST+6, UTC+1
Locked
