| Summary: | Infinite loop recovering from broken statement inside broken property | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | JS Tools | Assignee: | Michael Rennie <Michael_Rennie> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | ||
| Version: | 6.0 | ||
| Target Milestone: | 6.0 M2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Michael Rennie
http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=1f818dc2f4e8efeb3b0140f0f39b15354c413ad2 Looks like I caused a regression when I merged the tolerant statement logic. Also found that returning null from our default tolerant wrapping could cause a loop since the checks are expecting 'undefined' (not a regression). (In reply to Michael Rennie from comment #1) > Looks like I caused a regression when I merged the tolerant statement logic. > Also found that returning null from our default tolerant wrapping could > cause a loop since the checks are expecting 'undefined' (not a regression). Looks like not a regression. While working on a test case I reproduced even with the first fix. Added a loop guard: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=773abd405479fb0a1e03ee71361bfba496398744 |