7 commits

Author	SHA1	Message	Date
Jonathan Gamble	1e9f97a612	LibThreading: Run BackgroundAction error handlers on the origin loop ... BEHAVIOR CHANGE: Don't call on_error if cancelled, just reject. Don't reject promise from the background thread. Prevent data race on cancelled flag.	2026-01-28 15:36:33 -06:00
Zaggy1024	786ea6c8f2	LibThreading: Use WeakEventLoopReference in BackgroundAction ... BackgroundAction already assumes the event loop is alive, now we can assert that it is.	2025-12-09 16:12:40 -06:00
Zaggy1024	3742138cc3	LibCore+LibThreading: Always wake the event loop when deferred invoking	2025-12-09 16:12:40 -06:00
Zaggy1024	2aaf53bd2c	Everywhere: Use a forward declaration for pointers to Threading::Thread	2025-09-22 17:28:21 -05:00
Timothy Flynn	5f9ed343b3	LibThreading: Pass ownership of a BackgroundAction result to its caller ... There is no need to create a copy of potentially expensive structures.	2025-02-10 16:05:43 +00:00
Timothy Flynn	f20aa82c27	LibThreading: Avert a reference cycle in BackgroundAction ... When a BackgroundAction completes, it resolves a Promise (stored on the BackgroundAction object) with a reference to itself. The Promise will never unset this resolved value, thus it will hold a strong reference to the BackgroundAction until it is destroyed. But because the Promise is owned by the BackgroundAction itself, we have a reference cycle, and neither object can be destroyed. The only user of BackgroundAction is the ImageDecoder process. The consequence was that the ImageDecoder process would never release any image data for successfully decoded images. To fix this, instead of storing the promise on the class itself, we can just create it as a local variable and pass it around.	2025-02-10 16:05:43 +00:00
Timothy Flynn	93712b24bf	Everywhere: Hoist the Libraries folder to the top-level	2024-11-10 12:50:45 +01:00

Renamed from Userland/Libraries/LibThreading/BackgroundAction.h (Browse further)