220613 - Printer settings saved with many backslashes in printer name

Status: RESOLVED EXPIRED

(Core :: Preferences: Backend, defect)

Description

[Oldrich Dlouhy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20030927
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20030927

The prefs.js file is growing after each start/end of mozilla.
It is caused by adding more and more backslashes to print.printer settings (name)

Reproducible: Always

Steps to Reproduce:
Map a network printer under Windows XP and use it in Mozilla.

1. Start Mozilla
2. End Mozilla

Actual Results:  
Size of prefs.js increases, more backslashes added to printer name:

print.printer_\\pc\printer 

changes to something like 

print.printer\\\\\\\\pc\\\\\\\\printer

Expected Results:  
Size/content of prefs.js does not change

Comment 1

[Oldrich Dlouhy]

Attachment: Initial preferences (only printer settings)

This is the initial prefs.js file stripped of all but printer settings

Comment 2

[Oldrich Dlouhy]

Attachment: prefs.js after few sessions of Mozilla

This is prefs.js file after running Mozilla few times, stripped of all but
printer settings

Comment 3

[Dan Nelson]

I'm getting this too.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031001

I just noticed it today, when my prefs.js hit 200MB.  I guess we can
congratulate the mozilla authors on writing robust string-parsing code :)

Comment 4

[Dan Nelson]

This has apparently been fixed; I haven't seen the problem in months.

Comment 5

[Gervase Markham [:gerv]]

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/

Comment 6

[Gervase Markham [:gerv]]

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.