Are you using alternative debuggers? I have discovered that the one I use will sometimes lock if I generate an error on quit. It may be something I am doing wrong so I will not name it here, but it was pretty pervasive. Make sure you don't have breakpoints in your closestack handler. It may be nothing but I have had problems with that before.
Bob On Sep 13, 2011, at 2:25 PM, william humphrey wrote: > I'm trying to track an occasional freeze crash of LiveCode. It happens when > I shut-down the stack after closing the Valentina database connection. I > have code that checks to see if the database is already shut down and my > error message comes up saying: "database already closed" and then it > freezes. Since the error message is able to come up what should I also > instruct livecode to show me there that will help me track what is causing > the freeze. Is there some kind of "debug" log that will show the very next > thing livecode is trying to do that causes the crash? I always get my error > message first everytime. > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
