1936809 - Japanese localization doesn't seem to be working in the crash reporter client

Status: RESOLVED WORKSFORME

(Toolkit :: Crash Reporting, defect)

Description

[Alex Franchuk [:afranchuk]]

A user reported the "failed to load localized strings" error was being displayed. The only reason that error would be shown is if something failed to parse (i.e., the localization files are located but can't be loaded). In other cases (like localization info missing entirely), we fall back to the bundled en locale data (which loads without error).

Perhaps we should change the behavior here to attempt to fall back to the bundled locale data in the event of any error. Aside from that, let's check whether there's something broken in the Japanese builds. It's not known yet whether the user installed a langpack or used a Japanese localized installer, however based on where that error occurs, the latter is more likely.

Comment 1

[Alex Franchuk [:afranchuk]]

I've tested with the Japanese-localized installer for the 133 release, however the localization files load without issue. I think the issue with the crash reporter client that was encountered could potentially be due to a corrupted installation.

Do you know how to generate a hash of a file? The omnijar file is too large to upload to bugzilla (I think), but if you could generate a hash (of any sort, just let me know which algorithm) of the omni.ja file within your Firefox installation, that could be an easy way to reveal the issue. On MacOS, the file can be found at Contents/Resources/omni.ja within the package.

Otherwise, you may want to try to re-install Firefox.

Comment 2

[akihiko.kigure]

I don't remember the exact version, but I've been updating Firefox over and over again.

I don't know.

I don't remember the exact version, but I've been updating Firefox over and over again.
I haven't installed it for a few years.
The only change in my environment is that I've upgraded my macOS.

Comment 3

[Alex Franchuk [:afranchuk]]

All right. You may want to try a fresh installation. It's possible an update was interrupted or was corrupted. We are planning to potentially include a check for corruption in the crash reporter client at some point, however for now it cannot help to diagnose this. If there is some corruption, it could account for the crashes you're seeing, too (though there is a known bug that matches up with that, so maybe not).

Comment 4

[Alex Franchuk [:afranchuk]]

In lieu of other related reports, I'm going to close this as it seems to work under normal circumstances. I've opened bug 1938340 to improve the encountered behavior, though.