10
edits
(Fix bullets.) |
(Add to summary.) |
||
| Line 16: | Line 16: | ||
** The dialog on e10s can potentially stop and re-show multiple times (theorized by :jimm). For example, if facebook.com freezes the content process for 12 seconds every minute, non-e10s will block while showing the dialog, while e10s will show the dialog, hide it after 12 seconds, and then reshow it, every minute. | ** The dialog on e10s can potentially stop and re-show multiple times (theorized by :jimm). For example, if facebook.com freezes the content process for 12 seconds every minute, non-e10s will block while showing the dialog, while e10s will show the dialog, hide it after 12 seconds, and then reshow it, every minute. | ||
** Slow script notices can occur in multiple tabs at once in e10s. This seems like a rare occurrence, however, so it shouldn't be significant. | ** Slow script notices can occur in multiple tabs at once in e10s. This seems like a rare occurrence, however, so it shouldn't be significant. | ||
* Code like '''setInterval(function(){var x=Date.now();while(Date.now()-x<12000){}},30000)''' can show the slow script dialog on e10s every 30 seconds, while on non-e10s it will only show it once until you select an option in the dialog. It's not really possible to account for what the script might have done on non-e10s while the slow script dialog is shown and the user hasn't selected an option yet. | |||
* :azhang thinks the measure isn't comparable this way - in the non-e10s case, the event triggers under slightly different conditions. | |||
Next steps: | |||
* See if it's possible to make the measure comparable between e10s/non-e10s, or mark it as a non-blocker if not possible. | |||
Technical details: | Technical details: | ||
edits