Runtime issue: Axe in frame timed out:

[cianevans]

We're sorry, there was an issue with axe-core:

ma@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3464:42
fa/i<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3456:15
setTimeout handlerfa@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3455:128
pa/<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3451:30
post@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/content.bundle.js:973:33
asyncca@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3433:16
pa@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3450:17
ya/</<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3532:19
c@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3215:23
defer@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3232:44
ya/<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3531:15
ya@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3529:18
yg/<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:15763:15
c@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3215:23
defer@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:3232:44
yg@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:15762:88
axe.run@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/axe-versions/latest/axe.js:16046:13
6109/<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/content.bundle.js:1085:49
async*6109/Bridge/<@moz-extension://4be212a7-c398-4ca8-a3a6-c0f397aea669/content.bundle.js:725:58

[straker]

Thanks for the issue. Could you perchance provide the URL that the issue occurred on, or maybe a code snippet that reproduces the issue? Without either of those there's not much we can do and will have to close the issue as unresolved.