Menu

#92 separator + texunit = GL stack overflow & underflow

unknown
closed-fixed
any
5
2014-07-08
2010-01-05
sistisette
No

Using [separator] and, even under a separate [gemhead], sending a [texunit N( message to a [pix_texture] object, can cause continuous "GL: stack overflow" and/or underflow messages for some values of N.

Steps to reproduce the bug with the attached patch:
1) open the patch (you need three images img1,2,3.jpg)
2) click on the create message to open the gemwin and start rendering
3) click on the lower-right number (connected to img2) and enter any integer value other than 0, for example 1 or 2

A few "GL stack underflow" messages will appear on the console followed by a continuous flood of "GL stack overflows" messages

Switching back to a value of 0 should stop the error messages.

- Doing the same with the upper pix_texture seems not to produce errors
- the one on the left does
(seems quite random, may be different from machine to machine???)

- if you remove the separator you won't get any error.

Tested on windows. I think Cyrille Henry can confirm it, I don't know on what platform.

Obviously in this case the [separator] is not needed at all, but I do experience the same problems in cases where the separator is needed.

Discussion

  • sistisette

    sistisette - 2010-01-05
     
  • IOhannes m zmölnig

    • labels: --> Pixes (pix_ objects)
    • status: open --> pending-fixed
     
  • IOhannes m zmölnig

    kind of fixed in SVN rev3081

     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • IOhannes m zmölnig

    • Owner: Anonymous --> IOhannes m zmölnig
    • OS: --> any
     
  • IOhannes m zmölnig

    • Release: any_operating_system --> unknown
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB