Jeremy wrote:
On Fri, Nov 28, 2008 at 01:30:05AM +0000, corvid wrote:
Jeremy wrote:
Is there any way to stop this happening, or do I have to postpone showing the dialog until Cache_process_queue() runs?
Postponing it sounds right to me.
Unfortunately, if I show the dialog from inside Cache_process_queue() just before it iterates over the clients then something *still* runs asynchronously while the dialog is up, which gets me a warning from the CCC about a call on a finished chain, followed by a segfault when I confirm the dialog and reload the browser window. If I delay the reload even further by doing it from inside a timeout then I still get the warning, but not the segfault. (Amended patch attached.) I don't understand the CCC well enough to know what I should be doing here. What now?
I don't know CCC either. I wonder whether the original patch gave that warning with 0.8.x.
When I was doing this from a DPI it all happened asynchronously and I ended up writing a a_Nav_reload_url() that reloaded all the browsers for a gicen URL. I thought that was pretty hacky but maybe it's the only way to make this work?