Closed Bug 155627 Opened 22 years ago Closed 22 years ago

Segmentation fault after OK-ing duplicate image loading dialogs

Categories

(Core :: Graphics: Image Blocking, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 110112

People

(Reporter: davor.cubranic, Assigned: morse)

Details

(Keywords: crash)

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020510 I have image and cookie blocking turned on. Pretty often (but not consistently reproducible), when I access a site for the first time that wants to both set a cookie and load images, I first get the cookie permission dialog, and then two image loading dialogs (both for the exact same host name). When I click OK in the second image dialog, there is a brief pause and then Mozilla crashes with a segmentation error. When I restart it and try to access the site, everything works fine because cookie and image loading manager already know the permissions for it (I don't get the dialogs again).
I have been able to consistently reproduce this bug when I have tabbed browsing turned on. Steps: 1. Cookie blocking, image blocking, and tabbed browsing (on middle click) should be turned on. 2. Try to open a tab for a site that will try to both load images and set cookies that your cookie and image managers don't know about (for example, http://www.novilist.hr worked for me). This works both if the site is accessed by a middle-click or control-return in the address bar. 3. A new tab opens for the site. Cookie manager asks for a permission to set a cookie: answer no. 4. Image manager asks for a permission to load an image: answer yes. 5. Image manager again asks for a permission to load an image: answer yes again. 6. Mozilla crashes with a segmentation fault: run-mozilla.sh: line 72: 30414 Segmentation fault $prog ${1+"$@"} I did not notice this happening on Mozilla 1.0 I have running on my XP machine.
Severity: normal → major
Severity: major → critical
Keywords: crash
This is why image manager no longer asks.... So the problem no longer exists. *** This bug has been marked as a duplicate of 110112 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
QA Contact: tever → nobody
You need to log in before you can comment on or make changes to this bug.