Ran
|
Jobs
1
|
Files
0
|
Run time
–
|
Badge
Embed ▾
README BADGES
|
travis-ci
<a href="https://github.com/zulip/zulip/commit/<a class=hub.com/zulip/zulip/commit/c5e5691ec9f7b9d7d4c3dacbb081a1d8f5366228">c5e5691ec<a href="https://github.com/zulip/zulip/commit/c5e5691ec9f7b9d7d4c3dacbb081a1d8f5366228">">Fix Tornado memory leak of handler objects. In </a><a class="double-link" href="https://github.com/zulip/zulip/commit/<a class="double-link" href="https://github.com/zulip/zulip/commit/2ea0daab193834bbffa56cc8e53e66e29c840e57">2ea0daab1</a>">2ea0daab1</a><a href="https://github.com/zulip/zulip/commit/c5e5691ec9f7b9d7d4c3dacbb081a1d8f5366228">, handlers were moved to being tracked via the handlers_by_id dict, but nothing cleared this dict, resulting in every handler object being leaked. Since a Tornado process uses a different handler object for every request, this resulted in a significant memory leak. We fix this by clearing the handlers_by_id dict in the two code paths that would result in a Tornado handler being de-allocated: the exception codepath and the handler disconnect codepath. Fixes #463.
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
3 | 686.3 (TEST_SUITE=production) | 0 | Travis Job 686.3 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|