1. 02 Aug, 2022 1 commit
  2. 18 Jun, 2022 3 commits
  3. 17 Jun, 2022 1 commit
  4. 02 Jun, 2022 2 commits
  5. 27 May, 2022 1 commit
  6. 12 Mar, 2022 1 commit
  7. 05 Mar, 2022 3 commits
  8. 03 Mar, 2022 5 commits
  9. 07 Feb, 2022 1 commit
  10. 29 Jan, 2022 1 commit
  11. 15 Dec, 2021 3 commits
  12. 02 Dec, 2021 3 commits
  13. 05 Oct, 2021 1 commit
    • Craig Turner's avatar
      doc: QtGL: fix textures being recreated · 180cc786
      Craig Turner authored and Jean-Baptiste Kempf's avatar Jean-Baptiste Kempf committed
      QOpenGLFramebufferObject::takeTexture is detaching the current texture
      and transfering ownership to the caller, and the texture was never
      destroyed afterwards. It was leading to a huge memory consumption and
      leak when using the sample app.
      
      From the documentation[^1] in Qt5:
      
          Returns the texture id for the texture attached to this framebuffer
          object. The ownership of the texture is transferred to the caller.
      
          If the framebuffer object is currently bound, an implicit release()
          will be done. During the next call to bind() a new texture will be
          created.
      
      [1]: https://doc.qt.io/qt-5/qopenglframebufferobject.html#takeTexture
      
      Co-authored-by: Alexandre Janniaux's avatarAlexandre Janniaux <ajanni@videolabs.io>
      For the commit message and cleaning the fix mostly.
      
      Fixes #25867
      180cc786
  14. 20 Aug, 2021 2 commits
  15. 01 Jul, 2021 9 commits
  16. 07 May, 2021 1 commit
  17. 02 Apr, 2021 1 commit
  18. 18 Feb, 2021 1 commit
    • Steve Lhomme's avatar
      libvlc: the setup/cleanup rendering callbacks can be called many times · e3ed8e2d
      Steve Lhomme authored
      In some cases the decoder might ask for a decoder device that will use the
      setup callback. But in the end it's not using the decoder device. Then the
      display module is created, without knowing about that decoder device (via a
      video context) and calls the setup callback again.
      
      Unless the decoder device that is created in the vout is passed to the display
      module, we need to allow those multiple calls per session.
      
      Fix the D3D11 sample to take this in account. The D3D9 sample already takes
      care of it.
      e3ed8e2d