Closed Bug 1154458 Opened 9 years ago Closed 9 years ago

[Camera] Video recording fails after a long (~44-minute) 720p video

Categories

(Firefox OS Graveyard :: Gaia::Camera, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: diego, Unassigned)

References

Details

(Whiteboard: [caf priority: p2][CR 822220])

1. Open camera app
2. Set in camcorder mode
3. Set video resolution to 720p.
4. Record a video.

The app will complain at around 44 minutes when the video is ~3.8G size with "You have run out of media storage space" [1] even though there is still space left on the sd card. I can even record another video after I see this error.

My guess is that we're hitting some file size limit.

[1] https://www.dropbox.com/s/ik9ukboudqyzbs7/2015-04-14%2013.53.22.jpg?dl=0
blocking-b2g: --- → 2.2?
That would be the file size limit of the FAT32 filesystem on the uSD card:

https://en.wikipedia.org/wiki/File_Allocation_Table#FAT32

Not much we can do about this without changing to another FS.
(I'm also pretty sure this is restricted to neither Flame nor v2.2.)
Summary: Flame v2.2 camera fails to recording a long 720p video → [Camera] Video recording fails after a long (~44-minute) 720p video
Does it lose what was already recorded?
Whiteboard: [CR 822220]
Whiteboard: [CR 822220] → [caf priority: p2][CR 822220]
(In reply to Andrew Osmond [:aosmond] from comment #3)
> Does it lose what was already recorded?

Nope. It keeps the recording on the SD card
(In reply to Mike Habicher [:mikeh] from comment #1)
> That would be the file size limit of the FAT32 filesystem on the uSD card:
> 
> https://en.wikipedia.org/wiki/File_Allocation_Table#FAT32
> 
> Not much we can do about this without changing to another FS.

Ah I see. That does make sense.
Blocks: CAF-v2.2-metabug
No longer blocks: CAF-v2.1-FC-metabug
Thanks mikeh
Status: NEW → RESOLVED
blocking-b2g: 2.2? → ---
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.