IOS table does not reuse how to save memory

Phenomenon:
There is a table, page layout, as shown below:


Cell's style is more complicated, if reuse, then scroll up and down Caton phenomenon is particularly serious, if not reuse, sliding up and down without Caton, very smooth,
But the memory is rushing up, turn over sixty-seven will memory warnings, everyone who has to resolve this problem, both to ensure the memory does not rise, but also ensures that no card sliding screen?
Thank

Reply:
You can go Code4app Site Search waterfalls flow source code, is the successor to do custom UIScrollView that mimic UITableView achieve cell multiplexing method, you can compile it, is not the card, there will be no memory problems.
I might give you a link directly to it: http://code4app.com/ios/% E7% 80% 91% E5% B8% 83% E6% 95% 88% E6% 9E% 9C-% E4% B8% 8D% E5% 90% 8C% E7% 9A% 84% E5% AE% 9E% E7% 8E% B0% E6% 96% B9% E5% BC% 8F/4fdfecd96803fa117f000000
Reply:
Well, okay, let me try, huh.
Reply:
@ Wangliangffaflgh

I looked at the waterfall flow, page layout is relatively simple, so use it can be created directly, there will be no Caton phenomenon.
But I used the Cell, each time re-create the time, it is very slow, there are too many styles. Therefore not suitable for use when creating temporary,

Itouch4 now loaded on two screens (10 records per screen), which also reported on the memory.

Now is when the acquired data per screen, you first create a Cell, the Cell is added to the array, when used, direct access to the page.

Now want to use queues to achieve, sliding, when data on the preservation of 30, more than the rest of the data, it is first removed. Do not know whether you can. First try. Oh
Reply:
Micro-channel circle of friends, but also this effect, but micro-channel circle of friends is very smooth sliding and sliding on the itouch4 also very smooth, it will not appear out of memory, it is another micro-credit technology to achieve?