1. 14 Jun, 2022 1 commit
  2. 13 Jun, 2022 2 commits
  3. 09 Jun, 2022 1 commit
  4. 07 Jun, 2022 2 commits
  5. 04 Jun, 2022 1 commit
  6. 28 May, 2022 1 commit
  7. 15 May, 2022 1 commit
  8. 07 May, 2022 1 commit
  9. 19 Apr, 2022 1 commit
  10. 12 Apr, 2022 1 commit
  11. 08 Apr, 2022 2 commits
  12. 30 Mar, 2022 1 commit
  13. 29 Mar, 2022 1 commit
  14. 20 Mar, 2022 1 commit
  15. 12 Mar, 2022 1 commit
  16. 04 Mar, 2022 2 commits
  17. 27 Feb, 2022 1 commit
  18. 30 Jan, 2022 3 commits
  19. 28 Jan, 2022 3 commits
  20. 03 Jan, 2022 3 commits
  21. 09 Dec, 2021 2 commits
  22. 02 Dec, 2021 1 commit
  23. 29 Nov, 2021 1 commit
  24. 22 Nov, 2021 1 commit
  25. 08 Nov, 2021 3 commits
  26. 29 Oct, 2021 1 commit
  27. 28 Oct, 2021 1 commit
    • Jonathan L. Verner's avatar
      When codestyle.py outputs too slowly (or unexpectedly), restart it instead of crashing. · a0b9d197
      Jonathan L. Verner authored
      When the `codestyle.py` is too slow in outputting data, the
      `processOutputStarted` function might miss them, release the
      `m_mutex` lock and set `m_stylechecker` to nullptr.
      
      When the data then later arrives, processOutputStarted is called
      again, however without `m_mutex` being held and `m_stylechecker`
      no longer valid. This eventually leads to a crash when dereferencing
      `m_stylechecker`.
      
      The current commit tries to fix this by checking that `m_mutex` is
      held at the start of `processOutputStarted`. If it is not, then we are
      in the "late data case". However, in this situation, we do not know
      the amount of data that should still arrive and basically the only
      way to solve the situation, is to kill the server (and start it again
      on the next run). So that is what we do.
      
      BUG: 444484
      a0b9d197