Bug 206401
| Summary: | [JSC] Eagerly purging JIT code when VM::deleteAllCode is executed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Yusuke Suzuki <ysuzuki> |
| Component: | JavaScriptCore | Assignee: | Yusuke Suzuki <ysuzuki> |
| Status: | NEW | ||
| Severity: | Normal | CC: | saam |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Yusuke Suzuki
Is it worth trying?
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Saam Barati
What do you mean by purging?
Yusuke Suzuki
(In reply to Saam Barati from comment #1)
> What do you mean by purging?
Destroying JITData / Baseline JIT code eagerly before collection and incremental sweeping happens.
Saam Barati
(In reply to Yusuke Suzuki from comment #2)
> (In reply to Saam Barati from comment #1)
> > What do you mean by purging?
>
> Destroying JITData / Baseline JIT code eagerly before collection and
> incremental sweeping happens.
Sounds reasonable
Saam Barati
Why do we need to do it before collection? Maybe we can make it hook into the baseline throw away code I’m going to write?
Yusuke Suzuki
(In reply to Saam Barati from comment #4)
> Why do we need to do it before collection? Maybe we can make it hook into
> the baseline throw away code I’m going to write?
To quickly shrink the heap if memory-warning is emitted (memory-warning is emitted, then we should shrink size quickly. We are destroying code a bit indirectly, which means, clearing reference, and scheduling a GC. But we can gain memory more directly without waiting later GC & incremental sweeping.)