summaryrefslogtreecommitdiff
path: root/src/lib/evas/canvas
diff options
context:
space:
mode:
authorCedric BAIL <cedric@osg.samsung.com>2015-01-20 18:27:59 +0100
committerCedric BAIL <cedric@osg.samsung.com>2015-01-20 18:46:08 +0100
commitc25ba993f6125ce402f6450e8ab82df8474cf91a (patch)
treeffbd7db96a586fe772899278644b78a3e2412b61 /src/lib/evas/canvas
parent201df16d6756a00ed6ca2bc42c9986d42bb3070f (diff)
evas: reduce potential memory hole in Evas_Object_Protected_State.
The main difference between 1.12 and 1.13 memory foot print is actually related to this two pointer to mask. I am wondering if there is not an issue here also has we do have a duplicated pointer. We have prev_mask and mask in both cur and prev state of an Evas_Object, but only mask and prev_mask from the cur state seems to be accessed. If we can remove two pointers from those state, we should have a decent win in expedite benchmark. Hopefully 300KB to win there (Close to half the additional cost in memory).
Diffstat (limited to 'src/lib/evas/canvas')
-rw-r--r--src/lib/evas/canvas/evas_object_main.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/evas/canvas/evas_object_main.c b/src/lib/evas/canvas/evas_object_main.c
index 208a29eac1..7c2ea944bd 100644
--- a/src/lib/evas/canvas/evas_object_main.c
+++ b/src/lib/evas/canvas/evas_object_main.c
@@ -28,7 +28,7 @@ static const Evas_Object_Map_Data default_map = {
28}; 28};
29static const Evas_Object_Protected_State default_state = { 29static const Evas_Object_Protected_State default_state = {
30 NULL, { 0, 0, 0, 0 }, 30 NULL, { 0, 0, 0, 0 },
31 { { 0, 0, 0, 0, 0, 0, 0, 0, NULL, EINA_FALSE, EINA_FALSE } }, 31 { { NULL, NULL, 0, 0, 0, 0, 0, 0, 0, 0, EINA_FALSE, EINA_FALSE } },
32 { 255, 255, 255, 255 }, 32 { 255, 255, 255, 255 },
33 1.0, 0, EVAS_RENDER_BLEND, EINA_FALSE, EINA_FALSE, EINA_FALSE, EINA_FALSE, EINA_FALSE, EINA_FALSE 33 1.0, 0, EVAS_RENDER_BLEND, EINA_FALSE, EINA_FALSE, EINA_FALSE, EINA_FALSE, EINA_FALSE, EINA_FALSE
34}; 34};