I have had a similar issue, and have filed a bug report - copied here:
When content is published as HTML and run on a retina ipad it causes safari to crash.
If you open the layers panel in the safari dev tools you can see that every smart shape has 8MB of graphics memory allocated, even if it is only a 20px square icon. This is because each smart shape is drawn as a canvas element which takes up the entire screen, even if only a small portion of the screen is required.
Once ~300MB of graphics memory is used ios kills the browser.
The Captivate html publishing code should be updated to use canvases more sparingly.
But also Safari should be able to fallback to software rendering rather than creating a layer for each canvas. So perhaps it is also worth filing a bug with the apple webkit team.
Our current work around is replace smart shapes with bitmap images, which is pretty ugly and a bad workflow.