Yeah it's a bug. I had the same problem. It turns out that when you release a web view, that thread (cond_wait) keeps running. If you instantiate a new web view without any preexisting web view using that thread, a new thread is born. But any new webviews you create after the first will use the same thread if that first one is still using it. (The thread starts in loadRequest: ) I solved this problem by keeping all webviews in an array that never gets released until the program terminates. You could probably have a dummy webview instead and load a request at program start, keep that dummy in memory, and release all the other webviews normally.
|
