Closed Bug 702993 Opened 13 years ago Closed 13 years ago

Today trunk 2.8a1 very buggy

Categories

(SeaMonkey :: General, defect, P4)

Other
macOS

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 703374

People

(Reporter: quicksilver8, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0a1) Gecko/20111115 SeaMonkey/2.8a1
Build ID: 20111115003002

Steps to reproduce:

Installed new today trunk 2.8a1. Very very buggy: all of web pages completely white and blank. Reinstalled 11/15/2011 2.8a1.
Severity: normal → critical
Priority: -- → P4
Hardware: x86 → Other
Severity: critical → major
Just downloaded today's trunk: nothing to do. Browser windows are always white and, above all, blank. Other components from Window menu, though, work: Mail & Newsgroups, Composer, Address Book and IRC Chat show windows OK. I keep using november 15 trunk.
http://kb.mozillazine.org/Browser.cache.memory.enable

please look if this is enabled currently it will fail loading any networked page :(
if it is on false
Rocco, would you mind trying in safe mode just to make sure it's not caused by an extension? Also, do you see any errors in the error console?
Well. I redownloaded latest trunk. Even open in safe mode, same situation. But, in both modes, I can see the console window. How can paste here a screenshot for you?
Stefan, I've emailed you a screenshot of Console window. There are several errors.
https://bugzilla.mozilla.org/show_bug.cgi?id=703374 <- this could be related from the behavior your report describes
Indeed... indeed. I set this in Debug subpanel of Preferences... in Networking section, I've set to true the first checkbox (Disable XUL Cache), and to false the other two. Now I've set to true the third: Enable Mem Cache, and now all of pages load correctly!
But... which are the correct settings for the Debug subpanel? I've told my settings for Networking. As for the other two, Debug and Events, I've set to true all. Is it correct? And as for Accelerator key? Which values are good?
After your answer, I'll set to RESOLVED this bug, thanks.
You can find out the default settings by switching to a new profile and look at the debug panel. This is really a dupe of bug 703374 which will be fixed with the next merge to mozilla-central.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Resolution: WORKSFORME → DUPLICATE
You need to log in before you can comment on or make changes to this bug.