Closed Bug 782139 Opened 13 years ago Closed 10 years ago

Delete temp picture files once the page is closed generated from mozGetUserMedia

Categories

(Core :: WebRTC: Audio/Video, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jsmith, Unassigned)

Details

(Whiteboard: [getUserMedia], [blocking-gum-])

Steps: 1. Call mozGetUserMedia with {picture: true} with a valid success/error callback 2. Inspect the stream object returned Expected: The object returned should provide no indication that something was written to the local filesystem without the user knowing. The picture should represent an in-memory reference. Actual: A JPEG image file is written on Windows to C:\Users\<user>\AppData\Local\Temp. This seems incorrect - we shouldn't be polluting the user's temp folder with images generated by a picture taken - I would think this should be an in-memory reference. Not only that, but we shouldn't assume that the temp folder is always wiped immediately after a short period of time (days, hours) - Checking my folder right now, I still have pictures generated from the API as old as 7/13/2012. As a result, I've got around 90 pictures in that folder right now sitting around collecting harddrive space. We should do something better here.
Whiteboard: [getUserMedia]
Summary: Calling mozGetUserMedia with {picture: true} - Writes to user's temp folder as a JPEG, should keep object in memory → Delete temp picture files once the page is closed generated from mozGetUserMedia
Whiteboard: [getUserMedia] → [getUserMedia], [blocking-gum+]
Whiteboard: [getUserMedia], [blocking-gum+] → [getUserMedia], [blocking-gum-]
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.