Fixed stack overflow bug when calling undefined field #568
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed the stack overflow bug :D
This is the example code that caused it:
Symbol
when it should only check forObject
in GetField/Const , this was from when we did not have symbol primitives (pre-Object specialization #419 ) (this is another bug).Array.prototype.indexOf
they don't stop the tester but they "freeze" it (iterate from 0 to a very large number likeu32::MAX
).Now it reaches a lot more, but still gets stuck by
indexOf
in some tests.