@pc_bel: nothing was changed on the recording speed side; I bet any difference is because of different scene complexity. Please test the stack overflow bug first.
@garry23: Lua changes are a bit too much when I'm troubleshooting a memory corruption bug. The changelog from the Experiments page is valid.
Is this mean we could get a semi brick or definitive brick ? What is the long-term risk ?
Yes, as with all ML builds. Explained a little
here and also somewhere in the Tragic Lantern threads. Currently I'm diagnosing
this report, and it appears to be, indeed, caused by some bad settings reflashed by Canon code into ROM - possibly after memory corruption caused by ML.
The warnings from the download page are not there for fun - this kind of errors cannot be prevented on the current processor design, as it doesn't have a MMU (also valid for many other simple CPUs that use non-volatile storage updated frequently). Canon started to use a processor with MMU
with DIGIC 7, but they don't seem to use its memory protection features (they simply do a flat memory mapping, except a 0x1000-byte block unique to each core).chd
Just in case, make sure you have a copy of your ROM in a safe place (any recent installer tells you how to do so).