BUG: Timepicker does not display AM/PM on Ubuntu, Datepicker displays an arbitrary “October”

Datepicker and Timepicker Screenshot

Datepicker and Timepicker Screenshot

I recently noticed a little bug in firefox (I don’t know where this belongs, in “xulrunner” or in firefox code itself), and I dutifully report it here:

My friend built an extension for firefox, and I noticed that the timepicker control (in xul) does not display the AM/PM select, neither does it provide a 24 hour clock. (only on Ubuntu).

I live in India, and so it just shows IST instead of AM/PM (see screenshot)

This problem occurs only on Ubuntu (I have not tried other distros). The same firefox extension was displaying AM/PM correctly in Firefox when running on Windows Vista.

The same problem occurred with the datepicker control: it was displaying an arbitrary “October” between the Day number and Month number. (This too, only on ubuntu).

I have reported the bug at bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=479069

I wonder why this is hapenning.

How firefox eats up my system resources

Despite all the cool stuff about firefox, it can voraciously eat up system resources when spiced up with just the right add-ons. When I first noticed this myself, I was pretty surprised: I though firefox was the Best app ever! Now I’ve grown wiser, and I know better.

Here’s how firefox eats up my RAM: and the steep cliff on the graph is the moment I close firefox.

I’ve tried to reduce this stat ever since I got the (horrifying!) pic

For one, I reduced the amount of data firefox would store in its online cache (yea, that means your RAM) by reducing its cache size from 50MB to 20MB (change it from about:config -> browser.cache.disk.capaciy )

I’ve also removed the addons I don’t use, or are redundant. Like, I used to use flashblock, but since I’ve started using NoScript (which also blocks flash), I’ve removed the former.

This brings me to flash. Flash stuff on websites tends to make firefox eat up even more of system resources. It is best to kep flash disabled and enable it only for certain websites (using NoScript or flashblock). Anyway flash violates all known and loved rules of web design anyway. Who wants flash? Go away!

Back to where I left off: I also checked the problematic addons list and removed all addons that have a history of memory leaks. In some cases even a solution for problems was available, like the case of noscript and flashblock.

Well, I’m not complaining. I still like firefox more than I do any other browser. And I am fiercely loyal to it. This is just how I try to coax my favourite (and most frequently used) application from not mauling my RAM every time I run it.