Earlier today I started a ticket via email with IPS support regarding this issue. I wasn't sure posting to the forums was the proper avenue here. Turns out I probably should have instead of posting the ticket. The reason I say that is because I think it might be good to see if any other boards are experiencing this same issue. The issue at hand is as the title says; Tweet embeds causing pages to crash upon load.
@Jim M was the IPS Support Staff who so graciously helped me with my ticket. Unfortunately he was unable to reproduce the issue on my board and thought that quite possibly the problem might be on Twitter's end, as they may have issued an update that is causing the matter.
What we know - it seems to only affect Apple devices - iPhones and iPads (not sure at this point about it affecting any desktop machines). The browser in question seems to be Safari 15.3. It also seems to be random. In that, it doesn't appear to affect thread pages with the same conditions. These conditions would seem to be just having Twitter embeds located on it. The first I became aware of the issue was a thread with only two posts on it and it was only the second post that contained any Tweet embeds (2). The next report was on a thread that was 48 pages long. The 48th page started to crash after it had about 6 or 7 posts to it and 5 of them contained Tweet embeds. After the thread got to the 49th page, peeps stated that they could load that 49th page, just not the 48th.
We have many threads that have tons of Tweet embeds and these Apple device users claim that they load fine. It is quite an odd situation to be sure.
Hopefully you are not experiencing this issue, but if you are, if you could post your experience, maybe it would help to solve this issue. I for one would be greatly appreciative to get this resolved. I will update myself as, since I have put this matter to the general forum, it seems more are reporting the same experience. I might add that this has only propped up in the last 5/6 or so. Please be specific to include the device, browser and version experiencing the issue.
Thanks!