Comment 2 for bug 1632556

Could you please provide more information on your use cases? In normal usage you cannot get json decoding exceptions for jsons that were produced by the very same application. And if the corrupted json was put there by someone else hanging until it fixed back by the user might be a reasonable behavior