Closed Bug 288566 Opened 21 years ago Closed 20 years ago

Calling URLSimpleDownload() from plug-in often freezes

Categories

(Core Graveyard :: Embedding: Mac, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: brian, Assigned: ccarlen)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.5.7 (KHTML, like Gecko) Safari/125.12 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050331 Camino/0.8.3 In my plug-in I will occasionally call URLSimpleDownload() or URLDownload() to download a file from an HTTP address. This works 100% fine with Safari, but with Camino, Netscape, or Firefox it only works 50% of the time. What happens is that when URLSimpleDownload() is called it simply locks up. No errors or anything, but it just freezes and I have to force-quit the browser. It only freezes like this when the plug-in is streaming a SRC file at the same time. It's as though URLSimpleDownload() is waiting for the other stream to complete before it will work, but since URLSimpleDownload() is a blocking call, nothing can happen. I don't know what could cause URLSimpleDownload() to not work since it should be totally independant of the browser, but this is very reproducable, and like I say, it works 100% correctly with Safari. It's only on these other Mozilla browsers that it does this about every other time I try. Reproducible: Sometimes Steps to Reproduce: After a plug-in's NPP_NewStream() function gets called try calling URLSimpleDownload() to download some other file from an HTTP (or FILE) URL. 50% of the time you do this URLSimpleDownload() will freeze causing the whole browser to freeze.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.