Well, the first step is to avoid GC. So: 1. Is the frontend triggering GC, by making a lot of garbage? If so, something like comment 3 suggested approach 2 is the only way. 2. If not, is there any realistic way to avoid GC? This style of code rapidly consumes a huge amount of memory but generates no garbage at all (that is, all of the arrays are ultimately stored in a global variable, and thus rooted). But it would be unsound to *assume* that the code doesn't generate garbage. jonco, any ideas?
Bug 1530212 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Well, the first step is to avoid GC. So: 1. Is the frontend triggering GC, by making a lot of garbage? (I sort of doubt it, but if so, something like comment 3 suggested approach 2 is the only way.) 2. If not, is there any realistic way to avoid GC? This style of code rapidly consumes a huge amount of memory but generates **no** garbage at run time (that is, all of the arrays are ultimately stored in a global variable, and thus rooted). But it would be unsound to *assume* that the code doesn't generate garbage. jonco, any ideas?