Open Bug 550370 Opened 16 years ago Updated 2 years ago

lots of aborts on voxel rendering demo

Categories

(Core :: JavaScript Engine, defect)

defect

Tracking

()

People

(Reporter: vlad, Unassigned)

References

(Blocks 1 open bug, )

Details

Here's TMFLAGS=abort: Abort recording of tree http://voxel.onaluf.org/render.js:104@159 at http://voxel.onaluf.org/render.js:138@928: No compatible inner tree. Abort recording of tree http://voxel.onaluf.org/render.js:104@159 at http://voxel.onaluf.org/render.js:138@928: No compatible inner tree. Abort recording of tree http://voxel.onaluf.org/render.js:104@159 at http://voxel.onaluf.org/render.js:138@928: No compatible inner tree. Abort recording of tree http://voxel.onaluf.org/render.js:95@9 at http://voxel.onaluf.org/render.js:104@159: No compatible inner tree. Abort recording of tree http://voxel.onaluf.org/render.js:95@9 at http://voxel.onaluf.org/render.js:146@1144: Inner tree is trying to grow, abort outer recording. Abort recording of tree http://voxel.onaluf.org/render.js:95@9 at http://voxel.onaluf.org/render.js:118@537: Inner tree is trying to grow, abort outer recording. Abort recording of tree http://voxel.onaluf.org/render.js:104@159 at http://voxel.onaluf.org/render.js:138@928: No compatible inner tree. Abort recording of tree http://voxel.onaluf.org/render.js:95@9 at http://voxel.onaluf.org/render.js:118@537: Inner tree is trying to grow, abort outer recording. Abort recording of tree http://voxel.onaluf.org/render.js:104@159 at http://voxel.onaluf.org/render.js:139@973: Inner tree is trying to grow, abort outer recording. Abort recording of tree http://voxel.onaluf.org/render.js:95@9 at http://voxel.onaluf.org/render.js:118@537: Inner tree is trying to grow, abort outer recording. Abort recording of tree http://voxel.onaluf.org/render.js:104@159 at http://voxel.onaluf.org/render.js:139@973: Inner tree is trying to grow, abort outer recording. trace stopped: 3531: non-stub getter trace stopped: 12736: name() not accessing a valid slot (8fps vs. 40fps in chrome)
Deeply nested loop. We fail in the innermost loop, so that propagates outwards. We have to figure out why NAME isn't traced there.
Blocks: 550389
For what it's worth, I don't see the name() fail that vlad's seeing... All the aborts I see are inner tree trying to grow or no compatible inner tree. Those shouldn't cause blacklisting, right? I also see lots and lots of LOOP exits (tens of thousands), even if I get rid of all the MISMATCH exits. See bug 550391
Assignee: general → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.