You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please consider the following contrived usage of Polymer.Base.async:
<linkrel="import" href="../polymer/polymer.html"><script>functionAsyncAlpha(){// Queue a task:Polymer.Base.async(function(){console.log('alpha');// Cause a second task to be queued:AsyncBeta();// Throw an exception before the first task returns:thrownewError('ANY ERROR');});}functionAsyncBeta(){Polymer.Base.async(function(){console.log('beta');});}AsyncAlpha();</script>
The above example will cause the first task ("alpha") to be re-called in what is effectively an infinite loop. In order to reproduce this condition, a second task ("beta") must be queued before the first task returns, and an exception must be thrown after the second task is queued but before the first task returns.
The text was updated successfully, but these errors were encountered:
Yes I had the same issue, when I ported a rather complicated element from 0.5 to 1.0.
A JS error caused an infinite loop when it was thrown in an async callback.
@arthurevans yes, it's a dupe (sorry!). I looked for potential reports of this bug, but didn't notice #1759 for some reason. Thanks for noticing this 🍻
Please consider the following contrived usage of
Polymer.Base.async
:The above example will cause the first task ("alpha") to be re-called in what is effectively an infinite loop. In order to reproduce this condition, a second task ("beta") must be queued before the first task returns, and an exception must be thrown after the second task is queued but before the first task returns.
The text was updated successfully, but these errors were encountered: