Quote from: waterwingz on 04 / March / 2014, 18:27:09Added the ixus120 to my previous post. Less memory but probably still "normal" ?Just tried the g10. It's a DryOS r31 camera (like the d10), free UI mem is ~154000 when starting in play mode, and went below 100000 after some menu use. So it looks like UI memory usage is camera generation dependent. If Canon is OK with ~150kB after startup, it might be OK to reduce the UI memory somewhat on models that appear to consume less of it.
Added the ixus120 to my previous post. Less memory but probably still "normal" ?
ALL 165800MAX 165776
ALL 135856MAX 135856
ALL 351272MAX 351248
ALL 314264MAX 312880
Can we just malloc a lot of it and see what happens when the Canon UI starts to run low or actually runs out?
Quote from: waterwingz on 05 / March / 2014, 18:47:29Can we just malloc a lot of it and see what happens when the Canon UI starts to run low or actually runs out?You'll get an assert on the first failed allocation attempt The allocator is extern int _pvm_malloc(int handle, int size);
I was more wondering what the Canon firmware will do when its starts to run short of UI memory. Is the alert handled seamlessly so that the user does not see it? Does the Canon UI continue to run?
Started by Microfunguy General Discussion and Assistance
Started by mattkime LUA Scripting
Started by alexakc CHDK Releases
Started by fudgey General Discussion and Assistance
Started by selwonk11 General Help and Assistance on using CHDK stable releases
