What is the best practice for revokeObjectURL and calls it really necessary?

Question

I am in the process of writing an advanced image upload function for the site. In an attempt to resolve the entire image configuration before wasting time, and both client and server resources upload images to the server, I try to use HTML 5 functions to support a fully client component with mass loading after all image cropping and another editing was performed.

I have a drag and drop area on my page to allow multiple drag and drop files to actually select images for editing. On deletion, I create a list of image editors (using window.URL.createObjectURL ), with some form fields, a preview of the metadata, and I attach Jcrop to each image. The problem I am facing is when I attach Jcrop. Even though I bind the crop before canceling the url with a call to window.URL.revokeObjectURL , Jcrop does not seem to try to access the url until it's too late, and I get the missing images.

I resorted to the fact that I do not call revokeObjectURL at all, and this allows everything to work ... however, I'm not sure what is meant by it that does not cancel the use of resources. Does this allow the potential for memory leakage? Is the page being refreshed that frees the unreturned URLs of objects and their resources fixed?