Closed Bug 165698 Opened 23 years ago Closed 20 years ago

Big memory usage if many TT Fonts installed

Categories

(Core :: Internationalization, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: mrk, Assigned: shanjian)

References

()

Details

(Keywords: intl)

When I had many (>300) True Type fonts installed in my system, Mozilla 1.0/1.1 sometimes used >200MB memory during displaing some UTF-8 encoded pages (http://sed.pl/test.html for example). System Slackware 8.0, XFree86 4.2 without font server.
are you saying >300 fonts or >300 font files I have ~250 ttf font files, and memory usage went up to about 50MB. the testcase just displays a symbol and some '?' ==> Intl
Assignee: asa → shanjian
Component: Browser-General → Internationalization
QA Contact: asa → ruixu
Where are the TT fonts installed and what code accesses them? Do they show up in xlsfonts? or Are you accessing the TT fonts the direct FreeType2 code? (http://www.mozilla.org/projects/fonts/unix/enabling_truetype.html) Could you kindly please attach a -minimal- html page that displays this problem?
True Type fonts are included in FontPath (XF86Config) - avaliable for all X applications. xlsfonts displays them (I'm not accessing TT fonts via FreeType2) Minimal page that displays problem: http://sed.pl/test.html. In this page I included some strange characters encoded in UTF-8 - these characters are extracted from one of normal web pages.
Keywords: intl
QA Contact: ruixu → ylong
If I had to speculate I would first guess that the memory is used for the "per-char" metrics.
Reporter can you reproduce this bug with a newer build (1.4 final)? If not, then please close this bug as worksforme. Thanks.
shanjian is no longer working on mozilla for 2 years and these bugs are still here. Mark them won't fix. If you want to reopen it, find a good owner first.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
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
Closed: 21 years ago20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.