Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
This has been posted about before, but not so much as a bug (well, a similar one but without much of a testcase).
This testcase is pretty easy because it's the energy app demo that is packaged in ST 2.1 RC2. Just load it up on the iPad 1 in Safari. Click on Consumption. Click on All States. Bang, crash. Safari goes down.
I'm not sure what else you would need to reproduce this. It's pretty clearcut. I've experienced it in my app as well. I pared down my chart quite a bit, but I could never figure out any one thing that caused it. It was just when the chart got slightly complex, with several series, a legend, multiple y-axes, etc. You could comment out any one of those and it would be fine. But with everything on, it just blew up. And we're not talking about incredibly complicated charts.
But for now, just focus on the energy app and know that this is happening to quite a lot of people. Really looking forward to it being fixed for GA.
Still crashing with 2.1 GA. I realize the iPad has 256MB of RAM. Do you think your charting code eats that much RAM? You can reproduce this with a minimal set of data and a dozen or so series. I'd be surprised if the chart drawing code was that inefficient.