Quote:
Originally Posted by KevinH
Your log file showed the PV UpdatePage was rentered while waiting to load. Since that routine is not reentrant it caused PV to stop running javascripts.
So any really fast updating of tabs will cause the associated Preview to get caught trying a new load when the previous load had not finished yet.
|
This makes sense and definitely matches very often my activity (when doing s/r specifically).
Quote:
Originally Posted by KevinH
We will look into some type of preemption in loading Preview if that is even possible.
Your best bet to prevent cv->pv loss of sync is not to flash through pages in the tab manager, as loading a Codeview happens much much faster than loading a Preview and resolving all resources and then drawing the page to the screen.
KevinH
|
I'll try to slow down if it keeps happening.
Quote:
Originally Posted by KevinH
Okay, I pushed a potential fix to master to prevent reentrance to PV update page, that will delay a conflicting request to load a new page in the middle of a loading the previous page and then schedule a retry.
This should hopefully "fix" the speed demon approaches to loading Preview without causing cv->pv sync to break.
Those who are using test builds with debug enabled, please try a new build and report back.
This change also fixes the minimize/restore on my machine.
|
Brilliant.
Thank you so much. I've installed the new version, will try it out and let you know how it goes.