About: CHDK/Camera RAM memory usage

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: CHDK/Camera RAM memory usage Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

CHDK supports dozens of different Canon cameras, not all of which were created equal. One way they differ from each other is the amount of RAM memory available to CHDK. The camera is much like any other computer and CHDK uses the same RAM used by much of the camera's original functionality. The lack of RAM is a significant problem in some cameras, causing seemingly random crashes if too many features are enabled. Fortunately many things can be done to conserve RAM, read on. Things in RAM could be divided to 5 distinct groups: Developers, see CHDK Coding Guidelines for related information.

Attributes	Values
rdfs:label	CHDK/Camera RAM memory usage
rdfs:comment	CHDK supports dozens of different Canon cameras, not all of which were created equal. One way they differ from each other is the amount of RAM memory available to CHDK. The camera is much like any other computer and CHDK uses the same RAM used by much of the camera's original functionality. The lack of RAM is a significant problem in some cameras, causing seemingly random crashes if too many features are enabled. Fortunately many things can be done to conserve RAM, read on. Things in RAM could be divided to 5 distinct groups: Developers, see CHDK Coding Guidelines for related information.
dcterms:subject	Development CHDK internals
abstract	CHDK supports dozens of different Canon cameras, not all of which were created equal. One way they differ from each other is the amount of RAM memory available to CHDK. The camera is much like any other computer and CHDK uses the same RAM used by much of the camera's original functionality. The lack of RAM is a significant problem in some cameras, causing seemingly random crashes if too many features are enabled. Fortunately many things can be done to conserve RAM, read on. Things in RAM could be divided to 5 distinct groups: 1. * Static Canon variables: Always occupying a fixed amount of RAM. Nothing we can do about this part. 2. * Dynamic Canon variables: Allocated on-demand whenever Canon firmware needs RAM for something. If CHDK allocates too much RAM, it's possible that Canon's code will not get the RAM it requires and the camera may crash (typically it freezes and shuts down after a while with lens out). TODO: how much continous free RAM do our cameras require to be stable in everyday shooting? 3. * CHDK program code: Always there if CHDK is running. This part can be made smaller by disabling features in CHDK source code and then building and installing a customized version of CHDK. Note that Canon program code is not in RAM, it's in ROM. CHDK can't be put into ROM. 4. * CHDK static RAM requirements: Always there if CHDK is running. Becomes smaller by disabling some CHDK features. The developers have lately been optimizing the most memory hogging features by making them allocate RAM dynamically. 5. * CHDK dynamic RAM requirements: Required by CHDK while a certain feature is in use. This part can be smaller by not using some CHDK features that require RAM. If CHDK fails to allocate RAM, the feature probably fails to work. Unfortunately there is no low RAM warning or memory allocation failure error reporting to the user in CHDK currently. Note that if you just have enough memory to start a feature, it's possible that the camera crashes soon afterwards if Canon code is then unable to allocate memory. Developers, see CHDK Coding Guidelines for related information. Note there is experimental support for an alternate memory allocation system, which can increase the amount of RAM available to CHDK and reduce the amount of the original Canon heap used. See ExMem - enabling and loading CHDK into extended memory.

OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software