Acrobat abre 36 processos WebContent em 1 segundo e esgota a memória do iPhone (iOS 27.0)

Hi Amal, thanks for the quick reply. Here is the information you asked for:

1. Version currently installed (after the reinstall): 26.08.50 (20260917.135958). The Acrobat binary UUID in the new iOS log is the same as in my original report (f2353999-ea8d-3f88-b0ea-cd2271f005e7), so the Sept 27 incident happened on this same build.

2. Has it happened again: yes. On Oct 1 at 18:18:35 (UTC-3), during normal use of a PDF Space, on cellular data (not Wi-Fi). It was the second time I used a Space that day; the first time was fine. The app froze and iOS generated a new Jetsam report. It shows Acrobat launched 21 seconds earlier with 54 com.apple.WebKit.WebContent processes in its coalition, 51 of them spawned within a 0.3-second window, about 2.3 GB in total; the whole Acrobat group reached 2.57 GB resident. Free memory dropped to 73 MB and iOS killed system services (corerepaird: vm-compressor-thrashing; nsattributedstringagent: highwater). Excerpt below.

3. Any Space or a specific one: I have two Spaces. I later tested both with screen recording (open the Space, wait 1-2 minutes without the AI Assistant, then use the AI Assistant), and the problem did not reproduce in either recorded attempt.

4. Without the AI Assistant: in the recorded tests, opening a Space without the AI Assistant did not trigger it, and using the AI Assistant afterwards did not either. In the Oct 1 incident the burst of WebContent processes happened 21 seconds after launching the app; I can't say for sure whether the AI Assistant had already been opened at that moment.

5. Video: I have the two recordings of the steps (no reproduction in them) and can share them via a link if useful. Both freezes so far happened during regular use rather than in a test, so I will try again on cellular data with the screen recording on and post the video if it reproduces.

Excerpt from JetsamEvent-2026-10-01-181835.ips (iOS 27.0, 24A437), Acrobat coalition 1437:
- Acrobat pid 2176, 168 MiB, launched 21.4 s before the event, active/frontmost
- com.apple.WebKit.Networking pid 2183 (60 MiB) and the first WebContent pid 2181 spawned 16.7 s before the event; WebKit.GPU pid 2186 spawned 7.8 s before
- 54 WebContent processes in total (pids 2181-2239), 18-68 MiB each, 2283 MiB combined; 51 of them spawned between 1.7 and 2.0 s before the event
- Acrobat group total: 59 processes, 2566 MiB resident
- System memory at the time: free 73 MiB, wired 1627 MiB, compressor 754 MiB
- Killed by iOS: corerepaird (vm-compressor-thrashing), nsattributedstringagent (highwater)

I can share the full file privately if needed.

Thanks,

Complementando as informações que ficaram entre colchetes no relato:

- Versão do Acrobat: não anotei antes de reinstalar; o app estava instalado havia alguns dias e não sei se estava na versão mais recente. UUID do binário do Acrobat registrado pelo iOS nos dois eventos (26/09 e 27/09): f2353999-ea8d-3f88-b0ea-cd2271f005e7

- O que eu estava fazendo: tinha aberto um PDF Space e estava usando o Assistente de IA dentro dele.

- Como reproduzir: abrir o app → abrir um PDF Space → usar o Assistente de IA (perguntas/insights). Aconteceu pelo menos uma vez, em 27/09/2026 às 06:46. Já apaguei e reinstalei o app; informo aqui se voltar a ocorrer.