Recompiling the same code multiple times is wasteful, so normally the result is cached by the browser. However, this does not apply to chrome-extension:// URLs, as the compilation cache is integrated with the HTTP cache and there were security concerns if caching was enabled.