Closed
Bug 168498
Opened 23 years ago
Closed 20 years ago
CJK Character Corruption Under UTF-8
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: lingmuhebo0, Assigned: tetsuroy)
References
()
Details
(Keywords: intl)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
After Mozilla crashes several times, CJK characters become corrupt whenever
encoded in UTF-8. For example, bookmarks, the titlebar, Google.com (under
Japanese preferences), and the exported bookmark file when read in the browser.
CJK characters continue to appear, but the characters are different. Once the
corruption occurs, I have been unable to undo it.
The problem occured again after a fresh reinstall of Windows XP.
Reproducible: Always
Steps to Reproduce:
1. Install Windows XP
2. Install Mozilla 1.1
3. Bookmark websites where the title incorporates CJK characters, and write the
title down.
4. Crash it a few times.
5. Compare the CJK characters in the bookmarks from what it was before.
Actual Results:
The CJK character in the bookmarks did not match what it displayed before.
Expected Results:
It should have continued to display the same characters.
The crashes may have been due to lack of memory after loading several
applications with only 256 MB of RAM
Comment 1•22 years ago
|
||
It may be difficult, but try getting screenshots from a recent build showing
what is going on.
Comment 2•21 years ago
|
||
I've just tested this with a 1.7 branch build on windows XP and after logging
into my hushmail account and making several hushmail transactions (composing a
couple of mails, and reading a couple of mails) my memory usage trippled from
atartup at around 20MB to 58MB using hushmail. It didn't drop, according to
windows task manager, when I left hushmail and visited mozilla.org -- until I
minimized and restored the window, at which point it returned to about 21MB.
But this seems to happen with any Java site I visit. Take
http://java.sun.com/applets/other/Bubbles/index.html for example. If I start the
browser it's at about 20MB. I visit the Java bubbles demo and it jumps up to
just over 40MB. I leave the demo and go to mozilla.org and it stays at 40MB.
Minimize and restore the window and it returns to just under 20 MB.
this sounds a lot like bug 123191 to me.
*** This bug has been marked as a duplicate of 123191 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Comment 3•21 years ago
|
||
Asa, this bug isn't about hushmail and isn't about memory usage....
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 4•20 years ago
|
||
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 5•20 years ago
|
||
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
Closed: 21 years ago → 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•