[AC-2188] iOS: Severe memory leaks produced when appending/deleting/inserting rows to the table

Step 1. Open iOS instruments and set the filter to tiui Step 2. Put the code below into app.js and run it

function crTable(){
	var t=Ti.UI.createTableView({
			editable:true,
			className:'testing'
		});
		
		var tdata=[];
		for(var k=0;k<100;k++){
			tdata.push(Ti.UI.createTableViewRow({
				title:'hello'+k
			}));
		}
		t.setData(tdata);
		return t;
}

function tableWindow(){
	var win=Ti.UI.createWindow({
		backgroundColor:'#fff'
	});
	
	
	var table=crTable();
	win.add(table);
	
	
	//window close button
	var closeButton=Ti.UI.createButton({
		title:'Close window',
		top:10,
		zIndex:1
	});
	
	closeButton.addEventListener('click',function(){
		win.close();
		
	});
	win.add(closeButton);
	
	
	//rows append button
	
	var appendButton=Ti.UI.createButton({
			title:'Append table rows',
			top:50,
			zIndex:1
	});
	
	appendButton.addEventListener('click',function(){
		var rows=[];
		for(var k=0;k<10;k++){
			rows.push(Ti.UI.createTableViewRow({
				title:'row appended'+k
			}));
		}
		table.appendRow(rows);
	});
	
	win.add(appendButton);
	win.open();
}


var mainWin=Ti.UI.createWindow({
	backgroundColor:'#fff'
});
var openTableButton=Ti.UI.createButton({
	title:'Open new window with table'
});
openTableButton.addEventListener('click',tableWindow);
mainWin.add(openTableButton);
mainWin.open();

Step 3. Click the button 'open new window with table' Step 4. Click the button 'Append new row' or alternatively , swipe a table row to the left and delete it Step 5. Click the button 'Close button'. Step 6. Repeat from steps 3 to 5 several times. Description: The methods of the table such as ** table.appendRow(row) ** table.deleteRow(row) ** table.insertRowBefore(index,row), etc when used to alter an already existing table, produces severe case of memory leaks. The behaviour of the leaks is described below very precisely - *1.* Open the window containing the table. The table has about 100 rows in it. *2.* Click the button 'Append table rows'. *3.* After appending, close the window and watch the changes in the instruments . *4.* Repeat these steps until you can see only *TiUITableViewRowProxy* and *TiUITableViewCell* retained alone in the instruments with 13kb+ memory allocated to the former and about 5kb+ memory allocated to the later. Do not click again the append button or delete any rows until you get to see the expected result in the instruments so as to give a better view of the nature of leaks. *5.* As soon as you obtained the expected result, start it over again from the first step for the second time but this time, by clicking the append row button too. *6.* Close the window and inspect the memory in the instruments. *7.* Now the *TiUiTableViewRowProxy* goes up to about 26kb+ and *TiUITableViewCell* to about 10kb+ *8.* As you keep on repeating these steps, each time the window is opened and close, the *TiUITableViewRowProxy* and *TiUITableViewCell* memory allocation gets incremented every time by about 13kb+ and 5kb+ respectively and never gets cleared at all. _However, if you simply open and close the window( i,e if you don't append or delete any rows), every TiUI proxy gets cleared on windows closed( this does not mean that the memory leak that was induced earlier by the append/delete methods gets cleared too but they remain stuck forever and increases as you opens and close the window after appending/deleting/altering the table) ._