After fixing ICE-9331, it became apparent that similar problems could occur when coalescing custom application resources. The error was produced because a source file, that didn't end with a blank line and whose last statement didn't end with a semi-colon, was being concatenated immediately before another resource file, without inserting any characters in between, so the final result contained a syntax error, which was preventing the browser from interpreting the rest of the coalesced resource, causing undefined/"not found" type of errors.

While we could make sure to end all of our code with semi-colons (many function declarations are not doing this, perhaps because they already end with a closing curly bracket), many custom application source files, created by app developers, might ignore this rule, which could cause errors like the ones described in ICE-9331. So, it would be advisable to insert a blank line between each coalesced (concatenated) resource to prevent this kind of errors.