Closed Bug 25431 Opened 25 years ago Closed 25 years ago

Browser unable to display any URLS

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows 95

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 23709

People

(Reporter: simone, Assigned: jud)

References

()

Details

Using the 01-25-20 M13 build, Win32. This happens both when I migrate a profile or create a new one. The browser tries to resolve the URL, then displays a message to the effect of "Unable to locate <website>, please try again." I tried several URLs such as home.netscape.com, amazon.com, tinderbox, etc. Mail works just fine! My system is a Compaq LTE 5380 laptop, with 80.0MB RAM, running on ISDN.
Have you tried a newer build?
More data on my home system: I've installed this build on my D: drive since I didn't have enough space on C. Don't know if this makes any difference. The M13 build works great on my machine at work, btw. I've also experienced the same problem with more recent M14 builds, except I get a "timed out" message. JAR, sorry but I didn't know who to specifically assign this to.
Assignee: nobody → jar
This sounds pretty important... if it can be reproduced. I'm going to pass it to Warren, and hope that he can at least decide what group should have a look-see.
Assignee: jar → warren
Jud: Where does "Unable to locate <website>" come from? DNS failure? Simone: We need more data on how to reproduce this. Can you try to narrow it down? Thanks.
Assignee: warren → valeski
Target Milestone: M14
we pump that dialog (from nsWebShell.cpp) when a load returns NS_ERROR_UNKNOWN_HOST. Could this be another joyous Compaq (I'm so thankful that Dell surpassed them in sales last year) DNS issue (cc'ing gordon). I wonder if compaq packaged a nice homegrown winsock for some of their machine distributions? Simone, did IS build this machine for you, or did you get it out of the box from Compaq? Also, code that throws that dialog has changed a bit in the last couple of days, can you try a new build.
This is an IS-configured machine, it's about 3 years old. I can bring the machine in if you want to take a look-see. In the meantime, I will try today's build (1/31/00) and report back here.
more on this bug: I just installed today's build (1311), migrated a profile. Was able to display home.netscape.com, but then I got the "program performed illegal operation" message. I decided not to okay this dialog and keep going. Was able to start mail, get messages before the system hung. I restarted the build. While the browser was trying to resolve the netscape url got the message "connection was refused" even though it did display the page. Started mail succesfully and displayed one message that contained a URL and tried to open it (ZDNet.com). The browser displayed the URL then proceeded to the "illegal operation" message. I clicked the Details button and here's what it said: MOZILLA caused an invalid page fault in module NECKO.DLL at 014f:6055880c. Registers: EAX=70616373 CS=014f EIP=6055880c EFLGS=00010202 EBX=00000000 SS=0157 ESP=0153fd8c EBP=0153fdcc ECX=0b269850 DS=0157 ESI=0b269968 FS=3477 EDX=8166ef84 ES=0157 EDI=0b269850 GS=0000 Bytes at CS:EIP: ff 30 56 e8 44 33 00 00 83 c4 0c eb 05 bb 05 40 Stack dump: 00000004 00000001 0ad5b6f4 00000000 6055b087 0b269928 00000000 0b269220 0ad5b704 00000001 0ad5b6f4 00000000 6055b3f4 0153fdd4 00008e42 0153fe1e Hope this helps! I can bring the machine in tomorrow if anyone wants to reproduce this.
Well, the last crash described looks like bug# 23709, but the original description sounds like a separate bug. Let's not confuse the two...yet.
tever, thoughts?
QA Contact: nobody → tever
sorry Jud, I can't add anything to this. I am not having the url problem like described on 01-25 builds running on win 95.
I can't repro this. I'm marking it a dupe of the socket crasher. *** This bug has been marked as a duplicate of 23709 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
verified dupe of bug 23709
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.