If you drag and drop a file from Windows Explorer to
Drip, Drip will not detect any leaked elements.
Logged In: YES
This was fixed on the trunk (see
This change uncovers a thrown exception in some
difficult-to-reproduce situations, but it appears that the
exception is caught and Drip continues normally.
This bug also prevented leaks from being detected when links
were clicked. For example, using the address bar to go to
Yahoo revealed memory leaks, but clicking a link to visit
Yahoo (such as from another search engine) did not.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.