Anyway i add a suggestion (maybe for w3c): it is possible to remove revocation phase and add a algorithm similar to a gargage collector(checking references in dom and in js variables) also for blobs .Programmable revocation is a operation not easy in a complex GUI and add useless code for adding a block code you can put inside the browser.  

@cristian: Could you please provide us a sample test case or URL to check the issue from our end?

Thanks!!

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

It is not necessary to write complex logic for reproduce the bug. It happens in any case.
You have to write 2 code lines , one for importing a image (for example), one for revoking. 

Unable to triage this issue from TE-End, adding "TE-NeedsTriageHelp" for further triage.

Repro:

1. Load attached file
2. Open DevTools > Sources, expand '(no domain)'. Observe 'blob:...' URL
3. Click 'Revoke' button

I have no idea what a desirable UX would be here. 

Deleted: urlrevoke.html 469 bytes

urlrevoke.html 469 bytes View Download

Thanks for the repro!  Indicating which sources are revoked needs some UX work.

We don't have an event in devtools when blob URLs are revoked; thus the Sources/Application panels are not updated.

Closing as WontFix due to lack priority / resources.