issues with open and fopen while recording video

@outslider

Since you have an s2is now, can you check whether you have the following issue:
While the camera is recording a movie, can you select any script or start any module (like the file browser, module inspector, calendar, etc.)? If you try this, use a card with only a few MB free space, as the keyboard task may become locked until the recording stops.

I hope you don't mind this request (and sorry for the off-topic).

---

edit: fixed the title due to newer findings

@outslider

Since you have an s2is now, can you check whether you have the following issue:
While the camera is recording a movie, can you select any script or start any module (like the file browser, module inspector, calendar, etc.)? If you try this, use a card with only a few MB free space, as the keyboard task may become locked until the recording stops.

I hope you don't mind this request (and sorry for the off-topic).

Hello!

Ok, what I have tried while recording a movie:

- filebrowser works, but very slowly (listing another directory takes a lot of time)
- calendar works without problems
- text reader works - and loads text from file (by this slow fbrowse...)
- games kindly ask about changing mode to play:)
- I was able to load and even run my universal intervalometer, which made a few photos while making a movie (wow!)
- I was unable to load EDI editor - the camera hangs - movie is still recording, I can't turn off ALT mode, can't stop record, can't power off by button, camera doesn't respond on opening card door - it only responded when I removed the card - EDI has loaded for a few miliseconds and camera turned off right after that.

I did these tests on almost empty 2GB card - I hope you don't mind:)

Quote from: srsa_4c on 19 / May / 2013, 16:48:16

@outslider

Since you have an s2is now, can you check whether you have the following issue:
While the camera is recording a movie, can you select any script or start any module (like the file browser, module inspector, calendar, etc.)? If you try this, use a card with only a few MB free space, as the keyboard task may become locked until the recording stops.

I hope you don't mind this request (and sorry for the off-topic).

Hello!

Ok, what I have tried while recording a movie:

- filebrowser works, but very slowly (listing another directory takes a lot of time)
- calendar works without problems
- text reader works - and loads text from file (by this slow fbrowse...)
- games kindly ask about changing mode to play:)
- I was able to load and even run my universal intervalometer, which made a few photos while making a movie (wow!)
- I was unable to load EDI editor - the camera hangs - movie is still recording, I can't turn off ALT mode, can't stop record, can't power off by button, camera doesn't respond on opening card door - it only responded when I removed the card - EDI has loaded for a few miliseconds and camera turned off right after that.

I did these tests on almost empty 2GB card - I hope you don't mind:)

Not sure if it's significant or not; but the working stuff (module loading, text reader) use open/read, while the EDI editor Lua script uses fopen/fread (in the Lua code).

Phil.

Ok, what I have tried while recording a movie:

- filebrowser works, but very slowly (listing another directory takes a lot of time)
- calendar works without problems
- text reader works - and loads text from file (by this slow fbrowse...)
- games kindly ask about changing mode to play:)
- I was able to load and even run my universal intervalometer, which made a few photos while making a movie (wow!)
- I was unable to load EDI editor - the camera hangs - movie is still recording, I can't turn off ALT mode, can't stop record, can't power off by button, camera doesn't respond on opening card door - it only responded when I removed the card - EDI has loaded for a few miliseconds and camera turned off right after that.

Thank you very much for testing this. I expected this camera in the "can't open while recording" category, looks like I was wrong. First available fw is from April 2005, my two affected cameras are from a few months later.

I did these tests on almost empty 2GB card - I hope you don't mind:)

I just wanted to spare you that card removal

BTW, I haven't expected fopen() to behave differently, but tests now show that it causes hang on a greater number of cameras while recording a movie (ixus30/40, a410, s80, ixus65, s2is, more to come). Known models where open() is also affected still only include the s80 and a410 (fw build date is summer 2005).
If a mod feels like splitting this conversation into a separate thread, I'm not against it.

If a mod feels like splitting this conversation into a separate thread, I'm not against it.

Done. Wasn't really sure what the title should be.

A540 also hangs using edi, but not the others.

fopen handles use a bit more memory, but that seems unlikely to be the issue.

That could be one factor. But I have also tried runing EDI in new file mode, where it doesn't read/save anything before asked to do so. And even then it hangs... I have also observed hanging once I was trying to change parameters of a script in CHDK menu.

That could be one factor. But I have also tried runing EDI in new file mode, where it doesn't read/save anything before asked to do so. And even then it hangs... I have also observed hanging once I was trying to change parameters of a script in CHDK menu.

Saving the script parameter file using fopen/fwrite.
(I should probably change this.)

Phil.

Update: I've tested on the sx100 (DryOS r23) with a "special" Lua script (tries to open a file with io.open(), in "r" mode). Result: it hangs until recording is finished (I used the time-limited 160x120 mode). So, thread title is updated.

fopen handles use a bit more memory, but that seems unlikely to be the issue.

I suspect a system-wide file lock...

edit:
A460 (Vx, fw built in December 2006 (!)): both open() and fopen() cause hang.

Turns out D10 (Dryos R31) suffers from this too. Trying to open the file browser or calender hangs kbd_task.

The issue appears to have become even worse (noticed on the sx280, also present on the a3200, a3400). It's possible to enter, but impossible to leave ALT mode while video recording is in progress. Once it sticks, physw only gets unstuck after recording stops (automatically, for example on reaching a time limit).
I don't know that part of the code, but I suspect that a file operation is attempted upon leaving ALT mode.
Can anybody else reproduce this?