corrupted profile breaks web pages

RESOLVED EXPIRED

Status

()

Core
Networking: Cache
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Bernd Heinze, Assigned: Darin Fisher)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(3 attachments)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.4.1) Gecko/20031008
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.4.1) Gecko/20031008

http://color.twysted.net/ shows textboxes next to Red/Green/Blue instead of
sliders. Works fine with new profile. I don't know what is broken in my current
profile, but it shouldn't break, and if it's broken Mozilla should detect and
fix it. 
If you need detailed info on some files in my profile, feel free to ask.
I'll be attaching two screenshots as well.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

14 years ago
Created attachment 135584 [details]
How it looks in my case
(Reporter)

Comment 2

14 years ago
Created attachment 135585 [details]
how it should look
Are there any errors in the JS console?

If not, please attach your prefs.js and user stylesheet to this bug.
(Reporter)

Comment 4

14 years ago
Fehler: r.setMaximum is not a function
Quelldatei: http://color.twysted.net/
Zeile: 232

This error doesn't appear when using a new profile


var r = new Slider(document.getElementById("red-slider"),
document.getElementById("red-slider-input"));
r.setMaximum(255);
hmm... does clearing the cache in the "broken" profile help?
(Reporter)

Comment 6

14 years ago
clearing the cache doesn't help. neither clearing it through the preferences,
nor deleting the files in the cache folder manually. Do you need the prefs.js?
Does copying over the prefs.js to the working profile make it stop working?

Does the non-working profile have any extensions installed?
(Reporter)

Comment 8

14 years ago
>Does copying over the prefs.js to the working profile make it stop working?

yes

>Does the non-working profile have any extensions installed?

http://leodict.mozdev.org/ and i used to have http://tagzilla.mozdev.org/ installed
> yes

Then I'd like the prefs.js, please.
(Reporter)

Comment 10

14 years ago
Created attachment 135842 [details]
prefs.js
Hmm.... assuming the

Removed:
ldap2.
mail.
mailnews.

part was added by you, none of that looks wrong, really... does removing the
tagzilla prefs help (test in the clean profile you created that breaks when you
copy over this JS file).  Can you possibly narrow down to a minimal prefs.js
that shows the problem?
(Reporter)

Comment 12

14 years ago
Yes, the "Removed:" was added by me.

The problem seems to be cache related, however it doesn't seem to be a problem
with the cache folder itself, rather with the profile.

I copied the "bad" prefs.js to a new profile -> page looks bad

deleted all entries except: user_pref("browser.cache.disk.parent_directory",
"i:\\user\\foo\\12345");
As I didn't change any settings in the prefs file, the cache directory still
pointed to my "bad" profile. -> page looks bad
I deleted the Cache and Cache.Trash folder in my bad profile -> directories were
created, page looks bad
I deleted the entry, or pointed it to an empty folder outside the bad profile ->
page looks good

What files does Mozilla check before creating or acessing the cache?
Hope this helps.
To cache.  Darin, any idea what's up here?
Assignee: back-end → darin
Component: Profile Manager BackEnd → Networking: Cache
QA Contact: cacheqa
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.