Timothy Flynn 1ffda6a805 LibWeb: Propagate OOM in Body::fully_read() through its error callback ... Fetched bodies can be on the order of gigabytes, so rather than crashing when we hit OOM here, we can simply invoke the error callback with a DOM exception. We use "UnknownError" here as the spec directly supports this for OOM errors: UnknownError: The operation failed for an unknown transient reason (e.g. out of memory). This is still an ad-hoc implementation. We should be using streams, and we do have the AOs available to do so. But they need to be massaged to be compatible with callers of Body::fully_read. And once we do use streams, this function will become infallible - so making it infallible here is at least a step in the right direction.		2024-04-27 07:08:14 +02:00
..
Checks.cpp	LibWeb: Remove OOM propagation from Fetch::Infrastructure::Requests	2024-04-27 07:08:14 +02:00
Checks.h	LibWeb: Remove OOM propagation from Fetch::Infrastructure::Requests	2024-04-27 07:08:14 +02:00
Fetching.cpp	LibWeb: Propagate OOM in Body::fully_read() through its error callback	2024-04-27 07:08:14 +02:00
Fetching.h	LibWeb: Propagate OOM in Body::fully_read() through its error callback	2024-04-27 07:08:14 +02:00
PendingResponse.cpp	LibWeb: Use JS::HeapFunction in Fetch::Fetching::PendingResponse	2024-04-03 18:14:33 +02:00
PendingResponse.h	LibWeb: Use JS::HeapFunction in Fetch::Fetching::PendingResponse	2024-04-03 18:14:33 +02:00
RefCountedFlag.cpp
RefCountedFlag.h