[Webkit-unassigned] [Bug 175014] Frequent situations where iOS device locks up, requiring a hard reboot when consuming webrtc streams on IOS

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=175014

--- Comment #6 from andj2223 at gmail.com ---
Yes, you can share within Apple.

Alexey, It's unfortunate that you cannot see the information :( Is your actual email different than the one listed here? I'm getting replies from Youenn, so I know he can see it. If you send an email to my address, perhaps any spam blocking mechanisms on that side will be opened up. Youenn asked me some questions, so I'm sending the below to the private email thread. I'm posting it here so that Alexey can see it as well.

There seems to be some confusion. By "crash/hard lock", I mean that the entire iPad freezes and has to be hard rebooted (home button + sleep button). That is the only issue that I'm encountering -- "Crash" and "hard lock" are not two separate issues. I've changed the title to reflect this.

The application on the server also uses libwebrtc and is basically a screensharing app of sorts. More participants are not necessary to cause the locking. If the character is not quite smooth, that is not a big deal... that is not the issue that I'm describing. You can try interacting with the view ("use single finger drag, use two finger drag, use pinch, etc") and this may help with reproducing it.

> If you can try with an iPad with more memory, maybe the crashes will no longer happen which is why I do not see the crashes.
Regarding using an iPad with more memory: As I mentioned in my report that I'm using an iPad 12" which has 4GB. As far as I know, the most memory of any iPad. The hard lockup has still occurred many times, the logs that I provided were from that iPad. I suppose it could be a memory thing on the client side, but should a webpage really be able to cause an out of memory condition that locks up the iPad, requiring a hard reboot like this?

Some questions for Youenn and anyone else try to reproduce this:

Is there something more I can do on my end? More dignostic information I can provide?

If you weren't able to reproduce the issue, how long did you try to to reproduce the issue for? Unfortunately, I have had long periods (10+ minutes) where it works fine without hard locking, then immediately crashes on the next refresh. So it can be difficult to reproduce sometimes, and requires some patience, and many refreshes.

What version of iOS did you try to reproduce it on? I am using iOS beta 4. If you're using something newer (i.e. only available within Apple), I have not tested with that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170802/e8cd1809/attachment-0001.html>