Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Opengl thread conflict. #515

Closed
mb12 opened this issue Oct 29, 2014 · 5 comments
Closed

Opengl thread conflict. #515

mb12 opened this issue Oct 29, 2014 · 5 comments

Comments

@mb12
Copy link

mb12 commented Oct 29, 2014

The following error consistently reproduces. I've included the relevant stacktrace.

OpenGL Thread Conflict Detected

0x145af650(lldb) up
frame #4: 0x00291468 test_app`~VertexArrayObject(this=0x146ed65c) + 128 at vao.cpp:9
   6   
   7   VertexArrayObject::~VertexArrayObject() {
   8       if (vao) {
-> 9           glDeleteVertexArrays(1, &vao);
   10      }
   11  }
   12  

(lldb) up
frame #5: 0x002913c8 test_app`~VertexArrayObject(this=0x146ed65c) + 32 at vao.cpp:7
   4   
   5   #if GL_ARB_vertex_array_object
   6   
-> 7   VertexArrayObject::~VertexArrayObject() {
   8       if (vao) {
   9           glDeleteVertexArrays(1, &vao);
   10      }

(lldb) thread backtrace
* thread #9: tid = 0x1291c, 0x00e6df18 libglInterpose.dylib`__GPUTOOLS_HAS_DETECTED_AN_OPENGL_ERROR__, stop reason = breakpoint 1.1
    frame #0: 0x00e6df18 libglInterpose.dylib`__GPUTOOLS_HAS_DETECTED_AN_OPENGL_ERROR__
    frame #1: 0x00e6dffc libglInterpose.dylib`handle_opengl_thread_conflict + 80
    frame #2: 0x00fae22a libglInterpose.dylib`delete_vertex_arrays(__GLIContextRec*, int, unsigned int const*) + 522
    frame #3: 0x00291468 test_app`~VertexArrayObject(this=0x146ed65c) + 128 at vao.cpp:9
    frame #4: 0x00291468 test_app`~VertexArrayObject(this=0x146ed65c) + 128 at vao.cpp:9
  * frame #5: 0x002913c8 test_app`~VertexArrayObject(this=0x146ed65c) + 32 at vao.cpp:7
    frame #6: 0x002c33ea test_app`~DebugBucket(this=0x146ed654) + 54 at debug_bucket.hpp:19
    frame #7: 0x002c2df8 test_app`~DebugBucket(this=0x146ed654) + 32 at debug_bucket.hpp:19
    frame #8: 0x002bea40 test_app`~TileData(this=0x146ed60c) + 144 at tile_data.cpp:25
    frame #9: 0x002e4596 test_app`~VectorTileData(this=0x146ed60c) + 430 at vector_tile_data.cpp:21
    frame #10: 0x002e43c8 test_app`~VectorTileData(this=0x146ed60c) + 32 at vector_tile_data.cpp:16
    frame #11: 0x002afd5c test_app`std::__1::__shared_ptr_emplace<mbgl::VectorTileData, std::__1::allocator<mbgl::VectorTileData> >::__on_zero_shared(this=0x146ed600) + 40 at memory:3735
    frame #12: 0x3a5b2d84 libc++.1.dylib`std::__1::__shared_weak_count::__release_shared() + 52
    frame #13: 0x0029e9d2 test_app`~shared_ptr(this=0x145faf68) + 50 at memory:4448
    frame #14: 0x0029e980 test_app`~shared_ptr(this=0x145faf68) + 32 at memory:4446
    frame #15: 0x002c326e test_app`~work(this=0x145faf30) + 38 at uv_detail.hpp:121
    frame #16: 0x002c3228 test_app`~work(this=0x145faf30) + 32 at uv_detail.hpp:121
    frame #17: 0x002c31e0 test_app`uv::work<std::__1::shared_ptr<mbgl::TileData> >::after_work(req=0x145faf38, (null)=0) + 72 at uv_detail.hpp:145
    frame #18: 0x002563de test_app`uv__work_done + 130
    frame #19: 0x002567e2 test_app`uv__async_event + 38
    frame #20: 0x00256910 test_app`uv__async_io + 120
    frame #21: 0x0025888c test_app`uv__io_poll + 912
    frame #22: 0x00256b22 test_app`uv_run + 230
    frame #23: 0x002930ea test_app`mbgl::Map::run(this=0x15285c00) + 62 at map.cpp:110
    frame #24: 0x00298f1c test_app`operator(this=0x00000000, arg=0x15285c00) + 36 at map.cpp:86
    frame #25: 0x00298edc test_app`__invoke(arg=0x15285c00) + 36 at map.cpp:84
    frame #26: 0x002565f0 test_app`uv__thread_start + 16
    frame #27: 0x3b34f918 libsystem_pthread.dylib`_pthread_body + 140
    frame #28: 0x3b34f88a libsystem_pthread.dylib`_pthread_start + 102
    frame #29: 0x3b34daa4 libsystem_pthread.dylib`thread_start + 8
@springmeyer
Copy link
Contributor

@mb12 - thanks for the report. Will comment back when I can replicate.

@mb12
Copy link
Author

mb12 commented Jan 17, 2015

Closing it because it no longer replicates wit the latest update.

@springmeyer
Copy link
Contributor

@mb12 okay, thanks!

@kkaefer
Copy link
Member

kkaefer commented Mar 18, 2015

This is appearing again: #1016

@jfirebaugh
Copy link
Contributor

#1309

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants