It occurred to me that mach_msg_trap might indicate that the main thread is in fact healthy and just sitting there idling, and that the ‘hang’ symptom might be produced by some other thread. Here it is, in case that rings any bells with anyone:
Can you tell us what your app does at startup, relating to fetching data over the network and using / opening a database?
I wonder if that user’s sqlite db wasn’t closed properly and now it has problems unrolling the rollback or wal file that might be next to the main db file. Can you have the user check the sqlite db file that your app seems to work with?
Alternatively, maybe the db file is somehow locked. Have him try to move the db file somewhere save so that there is no more db file where you app may expect it, to see if that resolves the issue. If it does, you might want to figure out what’s wrong with the db. Maybe it’s in use by another app, or otherwise protected from being modified.
This is the strange thing - the application does not contain code related to sqlite nor accessing any other type of database.
Given that the app does not (knowingly) access any db file, are there any other likely operating system / RS framework related db files which are likely candidates for this which I could request the user to delete / reinstall / unlock?
Some other things which may be relevant: The application does use HTTPSocket and HTTPSecureSocket to communicate with some scripts on the internet via POST. It also makes basic use of an HTMLViewer to download and render a website.