Did you check "Miscellaneous -> Console -> Display last console" on the failed camera?
I wonder if that camera is still running the old build?
function cmds.build_stats() --e.g. to run !return mc:cmdwait('build_stats') local build_info ={} build_info = get_buildinfo() write_status(serialize(build_info), 'build_details')end
New test and screenshot of that attached
I added cameaside function:
!return mc:cmdwait('call return get_buildinfo()')
Previously, we introduced dofile as a kind of primitive operation to run chunks of Lua code. The dofile function is actually an auxiliary function; loadfile does the hard work. Like dofile, loadfile also loads a Lua chunk from a file, but it does not run the chunk. Instead, it only compiles the chunk and returns the compiled chunk as a function...[]...The loadstring function is similar to loadfile, except that it reads its chunk from a string, not from a file. For instance, after the code f = loadstring("i = i + 1") f will be a function that, when invoked, executes i = i + 1: i = 0 f(); print(i) --> 1 f(); print(i) --> 2
f = loadstring("i = i + 1")
i = 0 f(); print(i) --> 1 f(); print(i) --> 2
function cmds.call() local f,err=loadstring(mc.args) if f then write_status({f()}) else write_status(false,err) endend
If the arbitrary code is a cmds function then a subsequent mc:cmd("functionname paramrers") is required to execute the function
Unfortunately, this is going to make testing with philmoz build difficult. The only way I can think of to get back to a usable amount of RAM is the UI memory hack: https://chdk.setepontos.com/index.php?topic=11246.0
Is it possible to test for the original issue just on the cameras that did load ok, to see if either the EXMEM_TESTING or 'suba' checks detect anything? Or is the free memory so low that even this won't work?
Another option would be to change the EXMEM code to allow some of the memory to be used by CHDK and only run the EMMEM_TESTING at the end of the EXMEM block (which is most likely to be corrupted).
QuoteAnother option would be to change the EXMEM code to allow some of the memory to be used by CHDK and only run the EMMEM_TESTING at the end of the EXMEM block (which is most likely to be corrupted).That would probably make it a lot easier.
New test build.
It's a hack
The possibility that some previously reported crashes (prior to Phil's first test build) could, even then, be related to low memory availability,
In case of interest, attached are the pre/post (edit: record) memory stats using CHDK_LIGHT via the cli trace (after hub reconfiguration described above).
Started by superfly Feature Requests
Started by artanim Creative Uses of CHDK
Started by indian22 « 1 2 3 4 5 » General Discussion and Assistance
Started by ghust10 RAW Shooting and Processing
Started by amavroidis « 1 2 ... 5 6 » General Discussion and Assistance