forked from enlightenment/efl
and.... u get the idea. this made an n^m list of messages... where n was 3 of messages sent and m was # of child parts (42 of them)... this caused a silly 3 of timers to be allocated... don't ask how many. in a simple snapshot i saw 101mb of timers allocated... and i was just starting... anyway - this makes the propagatiopn not propagate down and then back up again... and it only needs 1 timer allocated to handle a re-schedule of processing messages. not N. "leak" that was just a massive memory spike) is now fixed. SVN revision: 65571 |
||
---|---|---|
legacy |