seen on linux commercial 2001-04-24-05-trunk -launch browser home page isn't loaded -click on throbber nothing loads -enter a URL nothing loads
note: windows commercial 2001-04-24-06-trunk works fine still waiting on mac build
could this be our old friend the cache corruption bug?
I don't see this problem on my Netscape build on Linux from 9pm last night
Chris - can you help with narrowing this down? thanks, Vishy
I've seen this randomly on linux, it's probably cache-related like Pinkerton said.
Definitely something to do with the cache. I seen several occurences where pages won't load any more, normally after a crash or a debug session which I've ended. Deleting the profiles's newcache/_CACHE_MAP_ appears to fix the problem.
I just loaded the same build on another linux machine....Used the same profiles that caused the crash on the original machine and did not have this problem. reducing from blocker and asking for help to clear up the smoketest machine for future testing...Thanks
what percentage of people are getting hit by this?
Please don't just delete the NewCache directory. We need to try things in this order: 1) COPY the NewCache directory somewhere outside the profile directory. 1) relaunch mozilla 2) reboot the OS and then relaunch mozilla (okay, if it's really too painful you can skip this, but it may affect the results). 3) DELETE the NewCache directory in the profile directory (or try to) and relaunch mozilla. 4) COPY the copied NewCache directory back into the profile directory and relaunch mozilla. If the browser works after 1, 2, or 4, the NewCache directory is not corrupt, but we will have narrowed the actual cause down. Please post results to bug 76293.
I have experienced this in Build 2001042404 under the following circumstances: Open Mozilla - somehow it crashes Open Mozilla again & no pages load. To fix this, I must first kill the Dr.Watson app on Win2K and then re-load Mozilla. It looks like stuff is staying in memory?
Yes, that's my hypothesis. I believe this is somehow related to open file descriptors to certain cache files (either left open after a crash, or previously opened by a another currently running instance of mozilla, as some linux users have reported). That's why I've asked people to try rebooting their OS after this problem occurs; that should definitely close the file descriptors, and allow the disk cache to start working again.
asa -> gordon.
This sounds very much like a dup of bug 76293. Someone can reopen this if they disagree. *** This bug has been marked as a duplicate of 76293 ***