[SERVER-26574] Avoid signals for JS interruptability Created: 11/Oct/16 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Platforms 2016-10-31 |
| Participants: |
| Description |
|
SpiderMonkey offers support for non-signal based interruption via JS_SetGlobalJitCompilerOption in JSJITCOMPILER_SIGNALS_ENABLE mode. This appears to solve the need for called code to guard against signals, as well as the general system instability caused by using signals (variables swapping values in js, other code crashing, etc). Switch to invoking those methods at runtime setup and re-enable periodic interruption |