New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gemvertexbuffer crashes on Intel without multicontext on destroy() #87

Open
avilleret opened this Issue Oct 29, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@avilleret
Contributor

avilleret commented Oct 29, 2014

to reproduce :

  1. open gemvertexbuffer-help.pd
  2. create a rendering window and start rendering.
  3. stop rendering and close the window.
  4. create a rendering window and start rendering again.
  5. close the patch

Pd crashes with this backtrace : https://gist.github.com/avilleret/a958e735e6da1b435e5b

This happens on Intel driver (ubuntu 14.10) but Nvidia doesn't seems to be affected.

Maybe tomorrow this will be gone itself :-)

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Nov 13, 2014

Owner

i can reproduce this.
using a backend that does not do context-sharing, (e.g. [gemglutwindow]) seems to work fine though.

Owner

umlaeute commented Nov 13, 2014

i can reproduce this.
using a backend that does not do context-sharing, (e.g. [gemglutwindow]) seems to work fine though.

umlaeute added a commit that referenced this issue Nov 13, 2014

implement "bang" and "render" msgs
this should allow to use single-buffered mode as it used to be.

Closes: #87
@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Nov 13, 2014

Owner

ouch, the reference in 5901d0a was an accident. it is a totally unrelated commit.

Owner

umlaeute commented Nov 13, 2014

ouch, the reference in 5901d0a was an accident. it is a totally unrelated commit.

@umlaeute umlaeute changed the title from gemvertexvuffer crashes on Intel without multicontext on destroy() to gemvertexbuffer crashes on Intel without multicontext on destroy() Nov 23, 2014

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Mar 27, 2015

Owner

just checked back on the theory with context-sharing, and indeed: when i change the context_sharing variable in gemglxwindow.cpp:674 to false, the crash goes away.

Owner

umlaeute commented Mar 27, 2015

just checked back on the theory with context-sharing, and indeed: when i change the context_sharing variable in gemglxwindow.cpp:674 to false, the crash goes away.

@umlaeute umlaeute added the bug label Nov 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment