Bugzilla

(In reply to Craig Arno from comment #30)
> A long time ago when this delay to start was first reported, it was suggested to me to set my display to "Events in the Next 14 Days".

Thanks for the tip, I can confirm that even with "Currently Selected Day" set in display options of unifinder, issue is still occurring.

That tip relate to Bug 1502923 which I have analysed at length for which some improvements were brought to light but issue never really sorted and pushed under the rug till better days by introducing workaround such as Bug 1502923 "Lazily load calendar unifinder tree" which help bring the loading down from 1H+ to 1mn+ at the time... as confirmed in Bug 1572823 Comment 19.

Since then though the situation has deteriorated to the point that since 77.x TB is Not Responding at startup and situation worthen with 78.x branch which cause registration of this bug... with my CalDAV calendar taking 10mn+ to load... nothing changed at my end apart from auto-updating TB.

Analysis above seems to suggest this bug is not related to Bug 1502923 so far. But I can't seems to get access to the async stack to see what happen when async function is run. 

As said previously, the performance report seems to suggest there are multiple imbricated call to async functions at the moment... which may not complete fast enough...

According to DevTool > Network, the network request appear and then seems stuck for a while (as seen in Devtool UI) with no access to the request details or response... till the next one is triggered after a long while... which get stuck as well... both request timing and Windows Task Manager shows that server responds in due time without much delay... the TB not responding seems appearing during the processing of each item in the response... items do appear one by one in the view but at a very slow pace like every 15-20s or more...

(In reply to Craig Arno from comment #30)
> A long time ago when this delay to start was first reported, it was suggested to me to set my display to "Events in the Next 14 Days".

Thanks for the tip, I can confirm that even with "Currently Selected Day" set in display options of unifinder, issue is still occurring.

That tip relate to Bug 1502923 which I have analysed at length for which some improvements were brought to light but issue never really sorted and pushed under the rug till better days by introducing workaround such as Bug 1502923 "Lazily load calendar unifinder tree" which help bring the loading down from 1H+ to 1mn+ at the time... as confirmed in Bug 1572823 Comment 19.

Since then though the situation has deteriorated to the point that since 77.x TB is Not Responding at startup and situation worthen with 78.x branch which triggered registration of this bug... with my CalDAV calendar taking 10mn+ to load... nothing changed at my end apart from auto-updating TB.

Analysis above seems to suggest this bug is not related to Bug 1502923 so far. But I can't seems to get access to the async stack to see what happen when async function is run. 

As said previously, the performance report seems to suggest there are multiple imbricated call to async functions at the moment... which may not complete fast enough...

According to DevTool > Network, the network request appear and then seems stuck for a while (as seen in Devtool UI) with no access to the request details or response... till the next one is triggered after a long while... which get stuck as well... both request timing and Windows Task Manager shows that server responds in due time without much delay... the TB not responding seems appearing during the processing of each item in the response... items do appear one by one in the view but at a very slow pace like every 15-20s or more...