I've found creating tables with 1000, 5000, 10000+ rows causes significant memory consumption and leaks. The URL provided is a 1.6MB file with approximately 6000 rows. Both Safari desktop and Safari on the iPhone grow over 40-50MB to render the page. This causes Safari on the iPhone to be killed by SpringBoard for using too much memory. Smaller pages of say, 1000 rows, appear to be creating memory leaks I cannot trace to my own code. Even after a UIWebView object is destroyed, it appears as though several MB of memory from the underlying objects are never released, meaning Safari on the iPhone will be killed off if the same 1000 row table is displayed more than a few times.