- User Since
- Mar 12 2020, 7:58 AM (184 w, 3 d)
Jul 1 2020
Apr 8 2020
I integrated your feedback and put a separate callback for just the clean up. To not do any further refactoring I placed it in OnFinished where also other resources of ThreadState are freed.
The cleanup accesses non of the previously freed resources and does not free any resources needed in the destructor called after it or the stat aggregation, which are the only functions accessing ThreadState afterwards.
Apr 3 2020
Making the ThreadFinish call into platform specific code caused all kinds of further issues.
Now the ThreadState itself owns and manages the ThreadSignalContext, as it is required on all supported platforms anyways.
Mar 26 2020
Mar 25 2020
Mar 24 2020
- The clean-up callback for the platform code is moved to a different part of the thread destruction sequence.
- Convert the test case to C instead of C++