No we run the Apis from our website and then to markets. Has a cache to allow us to freeze Apis before hitting the wallet if changed by the exchange. I was so caught up in the mint pal fiasco, didn't even think about the API being changed really. They've now disabled the API completely and we have froze it from our site.
My Bad for not paying close enough attention. Was busy being blown away by gox #2.
In considering though, it likely is a good idea to have a lite client as well. The more features in wallet, and In particular dealing with exchanges, the more problems can arise.
As well, some users may only want send receive balance and staking features, so a lite client as aback up or as a user preference might be a good idea.
We have tried numerous times to replicate the error and so far no luck. Can users confirm if these crashes were windows, Mac, or both?
Think there was 3 reports of crashes before situation was resolved.
Before you notified us of the cause and the fix, my (W764) wallet had crashed repeatedly as it was opening. Panic. Backup and remove wallet.dat (test app with fresh wallet.dat). Virus Checks. Download a fresh copy of app. Try another machine using same blockchain. Delete blockchain (without making a copy). Wallet still won't open. Reports here of similar problems. You report the fix. Left to redownload blockchain because of own carelessness. 18 hrs using blockchain.zip. Lots of time wasted (but not needlessly if lessons are learned).
Sorry about the shorthand, but that's it in a nutshell. Thanks for fixing it (but please update blockchain.zip). But my point is that we now have a proven mechanism that can remotely disable wallets. So the ability to reinstall the app without enabling the features looks like a priority... or a second 'emergency' wallet that enables transfer of funds. But that means maintaining Two wallets in sync. Mandatory upgrades will apply to Both. And that leaves room for more confusion.
PS
I also (carelessly) deleted the logfiles or I could pass them on to you. Sorry. There was an entry about being unable to make a connection, so I tested the app with the internet disconnected but it still crashed (although it remained open slightly longer before crashing). I used CClean to clear browser traces DNS and registry faults, but in retrospect I should have tried a more thorough registry cleaner.