The same leak audited in the X publisher exists wherever a video is streamed through a per-chunk request loop. Reproduced with the reported 49MB file: LinkedIn's plain Http::withToken() chunk loop grew to ~146MB (and it allows videos up to 5GB). Centralize the fix as freeChunkMemory() on the shared trait and call it (after unset) in the X, LinkedIn and YouTube loops so memory stays flat. Audited and left alone: TikTok and Instagram pull from a video_url (no local upload); Facebook and Bluesky stream the whole file in a single request. Adds a LinkedIn multi-chunk video test. |
||
|---|---|---|
| .. | ||
| Feature | ||
| fixtures | ||
| Unit | ||
| CreatesApplication.php | ||
| Pest.php | ||
| TestCase.php | ||