Closed Bug 271109 Opened 20 years ago Closed 20 years ago

Loading multiple tabs in background doesn't work, some websites not found.

Categories

(Camino Graveyard :: Tabbed Browsing, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: nevin_gawryluk, Assigned: mikepinkerton)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040825 Camino/0.8.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040825 Camino/0.8.1

When loading tabs in the background, from anything really but noticable more
when loading multiple tabs as from a bookmark folder, many tabs do not load and
report that the website was not found. Since URL's do not load in failed pages
(different  bug that's somebody's already reported) you can't reload the tab.
You can access it by typing in the web page or accessing bookmark for it and
hitting return.

Or if you loaded only one page and still got the page failed message the failed
URL is there and by hitting return on the failed address it will then load,
despite reporting that the website was not found the first time.

Reproducible: Always
Steps to Reproduce:
1. Set prefs to load tabs in background.
2. Select a folder with a number of tabs from various websites.
3. Open folder in tabs.

Actual Results:  
Some tabs loaded correctly, others reported that the website was not found.
Those were left with a loading... However the website was in fact there and
could be loaded by selecting it's bookmark or typing it in.

Expected Results:  
Opened all tabs with working websites.
This is an OS X issue and not something Camino can fix. So closing this bug as
invalid.

bug in lookupd causes the "site not found" error
when you request a page, a few things are happening:
1. You request www.example.com
2. Camino asks the OS to find an address for www.example.com
3. The OS checks to see if it has cached that address.
4. If it hasn't it asks the resolver.

lookupd is the bit of the OS that does the check.

if you HUP lookupd, the problem goes away for a while
HUP lookupd means
sudo kill -HUP `cat /var/run/lookupd.pid`
from the terminal
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.