Closed Bug 154701 Opened 24 years ago Closed 24 years ago

Trashing a saved web page renders the browser useless

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tracy, Assigned: mikepinkerton)

Details

Attachments

(1 file)

Seen on chimera build 2002-06-27-05-trunk -open a couple urls (tested with google.com & mozilla.org) -go back and forth between the two sites to ensure this ability -Save As.. one of the urls -go back and forth between the two sites to ensure this ability notice that one of these seems to load a file from cache instead of the url (seen in the status bar) -toss the saved page and the associated files into the trash bin -go back and forth between the two to ensure this ability the app is rendered useless. notice in the status bar: Read /Users/blah/blah/cache/blah. clicking links in the pages doesn't work, typing a new url into the url field seems to be active but just loads an empty page. (status bar has a perpetual Transfering data from site.com....) Winnie wasn't able to reproduce this at first. We then tried with clearing the cache previous to running the steps above. And then she could reproduce this bug. this is also reproducable if you had saved a different url, say cnn.com, in a previous run session, restarted the app, then trashed the saved cnn files. the app becomes useless. Note: deleting the files from a terminal does _not_ cause this bug.
Petersen, could you try to repro this? Tracy and I got different results. Depending on how reproducible this is, this could be a blocker.
wacky, can we break mozilla in the same way? Its like the cache redirects to the saved file, but that shoudln't happen
Assignee: saari → pinkerton
it would be interesting to see when this regressed. could it be due to conrad's file changes? cc'ing gordon and darin as well.
Attached file Crash log
I was able to repro this bug with the 6-28 build on OS 10.1.5. Unlike the original report, I didn't have to clear my cache this time. chimera also crashed shortly after I followed the steps in the original report. Crash log attached. After this crash, I was not able to use chimera at all, no matter which version I tried to launch. I tried launching the 6-28 build, the 6-27 build, and the 6-10 build with no success. The splash screen would appear for a few seconds and then I'd get a crash. Not sure if this problem has to do with this bug or the 6-28 build in general.
Does web browser persist use the wrong cache flags when saving, or something?
The default behaviour for webbrowserpersist is to fetch pages without specifying how they are cached (or not) http://lxr.mozilla.org/seamonkey/source/embedding/components/webbrowserpersist/src/nsWebBrowserPersist.cpp#162 http://lxr.mozilla.org/seamonkey/source/embedding/components/webbrowserpersist/src/nsWebBrowserPersist.cpp#1066 But you can override that behaviour and explicitly bypass or pull from cache by supplying your own load flags. http://lxr.mozilla.org/seamonkey/source/embedding/components/webbrowserpersist/public/nsIWebBrowserPersist.idl#44
this seems to be fixed as seen on build 2002-07-08-13 I can no longer reproduce this hang. when trying to access the deleted page. A dialog comes up istead of hanging.
wfm
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
I am seeing this again on build 2002-07-30-05 reopening
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
hmmm... i can't repro this with the 07-31 build
back to WFM as seen on build 2002-08-06-05
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: