> =return get_meminfo().free_size10:return:380008> =shoot()> =return get_meminfo().free_size12:return:379904> =shoot()> =return get_meminfo().free_size14:return:379904
All tests show a screen shot at 1 shoot and 100 shoots. Some tests have screen shots at 22, 33 and 51 shoots added, so you can observe leak progression.
for i=1,50 do local l,r=con:execwait('shoot();return get_meminfo().free_size') sys.sleep(500) printf("r:%s\n",r) end
Quote "Losing more when files / directories are deleted is odd. OTOH, it would be unexpected by the Canon firmware"Yes that is what I wanted show you here. Did you mean "expected?"
For example, running TEST 6 JPG&CR2 at 100 starts out at 200 bytes, then goes to 219, 223, and 226, part way through settling on 226 after 500 shoots. One obvious explanation is fragmentation.
Quote "It's very hard for me to think of a way this pattern would be caused by CHDK."What about this? ... it's is a guess based on pure imagination ... when Canon writes out the file it allocates memory resources and then when a dcimdl command (which may not necessarily malloc() anything) does its thing, those resources aren't deallocated.
In a sense CHDK does not know what Canon allocated hence it does not know what to free ?? I wanted to test|determine if Canon frees resources with with its *own* write/delete file, but it seems I can't get Canon to work while the camera is connected to CHDKPTP so I can't operate the camera and sniff memory "manually."
!r={}; for i=1,1000 do local s,m=con:execwait("click('set'); sleep(10); return get_meminfo().free_size"); r[i]=m ; end
The event appears random and I am sure this one is not memory related, because this last one happened at ~18 shoots. The link becomes disconnected with "ERROR download failed." The CR2 file is partially transferred, but camera does not crash, Fig 1. That is, without rebooting I can reconnect CHDKPTP, restart the shoot loop, and the old CR2 will be transferred correctly, Fig 2. What could this be?
deleting subdirs increases leak, although the ratio is not as high in the long test here. Your thoughts about patterns and where the leaks could be coming from?
What could you do?
My quote "What could you do? "Quote "Reboot before it gets too low, and don't delete unnecessarily."I know this and if I could afford rebooting I would not ask // I expected a technological solution idea we work out together somehow.
"What about this? ... it's is a guess based on pure imagination ... when Canon writes out the file it allocates memory resources and then when a dcimdl command (which may not necessarily malloc() anything) does its thing, those resources aren't deallocated. In a sense CHDK does not know what Canon allocated hence it does not know what to free ?? "Could you talk about this please?
Started by smilem General Help and Assistance on using CHDK stable releases
Started by SticK « 1 2 ... 70 71 » Creative Uses of CHDK
Started by SticK CHDK Releases
Started by andrew.stephens.754365 General Help and Assistance on using CHDK stable releases
Started by reyalp RAW Shooting and Processing