[SERVER-21711] make currentJSExceptionToStatus more robust Created: 01/Dec/15 Updated: 03/Dec/15 Resolved: 02/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 3.2.0-rc4 |
| Fix Version/s: | 3.2.0-rc6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Platform D (12/11/15) | ||||||||
| Participants: | |||||||||
| Description |
|
JS_GetPendingException can return non-object errors. We need to account for those properly if they show up. In particular, out of memory exceptions show up as strings |
| Comments |
| Comment by Githook User [ 02/Dec/15 ] |
|
Author: {u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}Message: JS_GetPendingException can return non-objects. In that case, just |
| Comment by Mira Carey [ 01/Dec/15 ] |
|
This masks the underlying oom condition |