flow 4a8abc948e
fix: prevent segfault due to callbacks into deleted objects
Since network requests are, for the most part, asynchronous, there's a
chance a request only comes through after the request sender has already
been deleted.

This adds a global (read static) hash table relating models for the mod
downloader to their status (true = alive, false = destroyed). It is a
bit of a hack, but I couldn't come up with a better way of doing this.

To reproduce the issue before this commit: scroll really quickly through
CF mods, to trigger network requests for their versions and description.
Then, in the middle of it close the mod downloader. Sometimes this will
create a crash.

Signed-off-by: flow <flowlnlnln@gmail.com>
2022-08-01 18:34:15 -03:00
..
2022-07-10 12:19:15 +02:00
2022-07-10 12:19:15 +02:00
2022-07-10 12:19:15 +02:00
2022-07-10 12:19:15 +02:00
2022-07-17 11:33:41 -03:00
2022-06-02 02:02:42 +10:00
2022-07-10 19:09:58 -04:00
2021-11-21 23:36:55 +01:00
2022-07-10 12:19:15 +02:00
Fix
2022-03-28 20:55:03 +02:00
2022-07-10 12:19:15 +02:00
2022-07-03 17:31:01 +02:00
2022-07-10 12:19:15 +02:00
2022-07-10 12:19:15 +02:00
2022-07-10 12:19:15 +02:00
2022-07-10 12:19:15 +02:00
2021-10-21 00:47:53 +02:00
2022-07-20 14:22:10 +02:00
2022-06-02 02:02:42 +10:00
2021-11-20 16:22:22 +01:00
2022-07-10 12:19:15 +02:00