1. 01 Apr, 2017 6 commits
  2. 26 Mar, 2017 2 commits
  3. 25 Mar, 2017 3 commits
  4. 22 Mar, 2017 2 commits
  5. 20 Mar, 2017 1 commit
  6. 17 Mar, 2017 1 commit
  7. 15 Mar, 2017 1 commit
  8. 14 Mar, 2017 1 commit
  9. 13 Mar, 2017 1 commit
  10. 12 Mar, 2017 1 commit
  11. 10 Mar, 2017 1 commit
  12. 09 Mar, 2017 1 commit
  13. 04 Mar, 2017 2 commits
  14. 28 Feb, 2017 1 commit
  15. 27 Feb, 2017 1 commit
  16. 25 Feb, 2017 2 commits
  17. 24 Feb, 2017 2 commits
    • Daniel Vrátil's avatar
      Merge branch 'Applications/16.12' · 471c1ae9
      Daniel Vrátil authored
      471c1ae9
    • Daniel Vrátil's avatar
      Fix crash when Connection is closed while ItemRetriever is running · 1593c17d
      Daniel Vrátil authored
      ItemRetriever::exec() runs a nested QEventLoop. If the parent
      Connection is terminated while the event loop is running, the
      delayed AkThread::quit() invocation is executed and the thread
      is destroyed, while technically there is still execution going
      on. To workaround that issue we don't destroy the thread in
      Connection::quit() if we detect a nested QEventLoop but instead
      we just notify the event loop to quit and destroy the thread
      later when execution returns back to ItemRetriever::slotNewData().
      
      This fixes a crash in QPSQLQuery, which was dereferencing a
      QPSQLDriver after the driver has been deleted as the thread was
      destroyed and avoids more of random crashes due to the Connection
      being virtually deleted from its own nested event loop.
      
      BUG: 374734
      FIXED-IN: 5.4.3
      1593c17d
  18. 23 Feb, 2017 8 commits
  19. 21 Feb, 2017 3 commits