UI memory - page 3 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 2 [3]   Go Down

UI memory

  • 24 Replies
  • 8907 Views
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: UI memory
« Reply #20 on: 05 / March / 2014, 18:47:29 »
Advertisements
Quote from: srsa_4c on 05 / March / 2014, 17:29:46
Quote from: waterwingz on 04 / March / 2014, 18:27:09
Added 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.
Can we just malloc a lot of it and see what happens when the Canon UI starts to run low or actually runs out?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline nafraf

  • *****
  • 1308
Re: UI memory
« Reply #21 on: 05 / March / 2014, 18:57:01 »
A495 - DryOS R43
Starting at play mode
Code: [Select]
ALL 165800
MAX 165776
After playing with Canon UI, lowest numbers found:
Code: [Select]
ALL 135856
MAX 135856

A810 - DryOS R50
Starting at play mode
Code: [Select]
ALL 351272
MAX 351248
After playing with Canon UI, lowest numbers found:
Code: [Select]
ALL 314264
MAX 312880
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: UI memory
« Reply #22 on: 05 / March / 2014, 19:02:11 »
Quote from: waterwingz on 05 / March / 2014, 18:47:29
Can 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);
Logged
*

Offline waterwingz

  • ******
  • 12138
    • Waterwingz
Re: UI memory
« Reply #23 on: 05 / March / 2014, 20:00:39 »
Quote from: srsa_4c on 05 / March / 2014, 19:02:11
Quote from: waterwingz on 05 / March / 2014, 18:47:29
Can 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?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline reyalp

  • ******
  • 14079
Re: UI memory
« Reply #24 on: 05 / March / 2014, 22:00:32 »
Quote from: waterwingz on 05 / March / 2014, 20:00:39
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?
It's a normal assert. The camera will write the romlog and shut down.
Logged
Don't forget what the H stands for.
Pages: 1 2 [3]   Go Up
« previous next »
 

Related Topics