Closed
Bug 193577
Opened 22 years ago
Closed 22 years ago
Some sites fail to load with latest Mozilla nightlies
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: raccettura, Assigned: asa)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030216
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030216
For some reason the past few nightlies fail to load Amazon.com (any page on the
site). I've tested this now on two networks (home, and school). Both fail to
connect, while IE, Netscape 4, and Opera all load the pages fine.
It says it's connecting on the bottom of the window, flashes like it's
downloading stuff... then it loads the blank page. When going to View->Page
Info, the page is about:blank.
No errors or anything.
Reproducible: Always
Steps to Reproduce:
<voice person="washed up Jurrasic Park actor">
1. Load Amazon.com
2. Look
3. that's it, there is no third step... there's no third step
</voice>
Actual Results:
amazon doesn't load
Expected Results:
should load page.
I can't find any other site that replicates this behavior. Doesn't seem like
Amazon changed anything. Works in older builds... so assuming this is something
with the nightlies.
Filing with Severity as Major until someone can provide some insight and lower
this. Sites not loading are a bad sign this close to a final release.
Comment 1•22 years ago
|
||
works for me - I was browsing amazon.com for quite a while with Friday's nightly
with no problems, and it still works for me now with 2003021508/win2k.
Reporter | ||
Comment 2•22 years ago
|
||
Got it working by deleting cookies. Appears something got corrupt in the
cookies as amazon.com's cookies had garbage for the expiration date... perhaps
that's what caused it. Don't know if that was due to the update, or a problem
on Amazon's site, or what... No other cookies appear to be affected (did a
spotcheck for similar problems).
Anyway. Can be closed as worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 3•22 years ago
|
||
Ok, I got a similar problem now with tvguide.com...
Says it's loading, goes through the motions, but nothing ever appears on the screen.
I deleted all cookies for the site. It replaced the cookies on reloading the
page (so something was transfered I assume) but once again, nothing.
I think something is definately wrong. Loads in all other browser.
If there is anyway I can debug this further and help find what the problem is,
please advise.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reporter | ||
Comment 4•22 years ago
|
||
Change Summary to "Some sites fail to load with latest Mozilla nightlies"
Summary: Amazon.com fails to load with latest Mozilla nightlies → Some sites fail to load with latest Mozilla nightlies
Reporter | ||
Comment 5•22 years ago
|
||
Build 2003011004 still exibits this issue. Once again a problem with amazon.com
and TVGuide.
Reporter | ||
Comment 6•22 years ago
|
||
Still trying to figure out what's wrong. I'm noticing dead images when loading
the amazon.com's search results.
Also noting that when amazon.com doesn't work, if i go to amazon.com/blablabla
the click on home, it loads (with image problems at times)...
No images are blocked in Mozila. List is empty.
Is there a way to debug this further?
Reporter | ||
Comment 7•22 years ago
|
||
Found something!
When I have the cashe set to "20000" (or any number)... this problem appears...
If I have it set to "0"... no problem.
Can someone else take a good look at this quick? I'm wondering what is going on.
How can I debug this further to provide more insight to reproduce this problem?
It's definately a bug, it's just a matter of getting others to see this behavior.
Reporter | ||
Comment 8•22 years ago
|
||
I've only seen this since 1.3b hence I'm putting a "?" for blocking1.3 so
someone takes a look and double checks that this is not some small manifestation
of a widespread issue.
Flags: blocking1.3?
Reporter | ||
Comment 9•22 years ago
|
||
I've only seen this since 1.3b hence I'm putting a "?" for blocking1.3 so
someone takes a look and double checks that this is not some small manifestation
of a widespread issue.
Assignee | ||
Updated•22 years ago
|
Flags: blocking1.3-
Assignee | ||
Comment 10•22 years ago
|
||
not a problem in 1.3 branch builds from today. Tested on winXP, RH8 and OS X 10.2.4
Flags: blocking1.3?
Reporter | ||
Comment 11•22 years ago
|
||
damn. What else can I do to debug this? I know it's a cashe problem. When the
cashe is set to 0 there is no problem. I tried clearing the cashe, and deleting
the cashe directory in my profile. That did not remedy the issue.
So it's either cashe off, or problems with a few sites. The only sites I know
of so far that trigger this issue are amazon.com's home page (and certain images
on the site) and tvguide.com.... I don't see a pattern. tvguide uses IIS,
amazon.com uses apache... so it's not a server issue.
Comment 12•22 years ago
|
||
still all works fine for me, using a 20030307 branch build on win2k.
try uninstalling mozilla, deleting any remaining files in the mozilla folder and
then reinstalling. if it still doesn't work, try using profile manager to
create a new profile to test with, and see if that works.
Reporter | ||
Comment 13•22 years ago
|
||
Works in a new profile.
I deleted the cashe directory, localstore.rdf... no success.
What else could I do?
I can't just forget this profile... email is important.
Comment 14•22 years ago
|
||
resolving WFM per reporter's comment.
first, back up your profile before you start messing.
copy your email, bookmarks, and other useful stuff from the old profile into the
new profile. http://www.kirun.co.uk/web/mozilla/mail.php may be helpful.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 15•22 years ago
|
||
The question still remains what caused it? Why did this happen? And how can it
be prevented?
Comment 16•22 years ago
|
||
Please try this :
close mozilla and delete :
profile\xul.mfl (only a XUL fastload file that will be regenerated)
profile\cert7.db, Profile\key3.db , profile\secmod.db (SSL Certificates)
Profile\cookies.txt , Profile\cookperm.txt (cookies and the cookie/image
permissions)
profile\cache\*.* (Browser Cache)
Comment 17•22 years ago
|
||
Unless you try to find the corrupt file (the cause) we can't answer that.
It could be caused by a mozilla crash while writing files, a system crash while
Mozills writes files or a corrupt FIle System.
Reporter | ||
Comment 18•22 years ago
|
||
What files should I be looking at? Anything to narrow it down? What exactly
would it look like? I have delt with corruption before, but not with Mozilla.
And I'm not nearly as compident with Mozilla's data structure, so I really don't
know where to begin in the profile.
Comment 19•22 years ago
|
||
you can delete the files i told you and you will loose near nothing.
You can also delete all files in Profile\Chrome\*.*
(You will loose additional installed Themes, languages packs)
after that i could be only a problem with the prefs.js....
See the release notes for the used Files...
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•