Closed
Bug 1015751
Opened 10 years ago
Closed 9 years ago
"streaming" video via image refresh crash in Fennec
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pierre.lin, Unassigned)
Details
(Whiteboard: [MemShrink:P3])
User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140506152807
Steps to reproduce:
I recently set up a Raspberry Pi system streaming video via the software "Motion" . This software uses a mini server of its own , and streaming video is actually a picture refreshed regularly (several times per second ) .
It is possible to access it via a streaming tools like VLC , but égallement via Firefox ( Chromium , Safari, and probably many others do not allow it) .
In the case of access via Firefox , it will begin to consume more and more memory, and after a few minutes it will crash , slow down the whole system, etc. .
In the context of access via the mobile version of Firefox from an Android phone (in my case a Samsung Galaxy s3 Mini. Android 4.1.2) , the entire Android system will shut down.
The procedure is simple , simply connect to the address of a site with a streaming flow came from Motion software ( creating a system recovering very many images may be capable of producing an equivalent bug , but I have not had the opportunity to test this case . )
This memory overhead could be so easily provoked voluntarily on any site , for example through the inclusion of a hidden iframe , and pointing to a flow of this type .
For convenience for your tests , I offers a streaming flow Motion for my Raspberry Pi to http://osaajani.no-ip.biz:8081 address.
Actual results:
Memory consumption of Firefox increases , slowing the system to a crash Firefox. For Android phones, the full Android system shuts down .
Expected results:
Il faudrait que le système vide correctement la mémoire, ou qu'il bloque tout simplement l'accès à ce type de flux. Dans tous les cas pour les systèmes Android le téléphone ne devrait pas s'éteindre.
can you open "about:crashes" and give us the ID of a submitted crash report associated with this issue? This could be an expected OOM crash or it could be security related.
The url given above does not appear to be active any longer and I can't seem to reproduce the issue.
Group: core-security
Flags: needinfo?(pierre.lin)
OS: Windows 8 → Android
Hardware: x86_64 → All
Summary: This bug exploits the creation of many images, and causes filling of the memory of the machine and in the Android phones causes an extension of the system (if tested on a samsung galaxy s3 mini). → "streaming" video via image refresh crash in Fennec
Updated•10 years ago
|
Group: core-security
Comment 2•10 years ago
|
||
It would also be good to know what about:memory looks like before it crashes. I'm not sure how to do that in Android Firefox.
Group: core-security
Whiteboard: [MemShrink]
Updated•10 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P3]
Comment 3•10 years ago
|
||
This looks like a multipart jpeg. Seth, I know we have some open issues about multipart jpeg, is this one of them?
Component: Untriaged → General
Product: Firefox → Firefox for Android
Version: 29 Branch → Firefox 29
Comment 4•9 years ago
|
||
No actionable info here, and it's been sitting too long. Closing it out.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(pierre.lin)
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•