Locating translation errors with Crash Finder

Crash Finder allows the user to isolate translations that cause crashes of the localized application, and catch the localization bugs at the early stage of the localization process.

Translated application crash may be caused by memory overlays due to string expansion, nonintended resource changes and errors in translation of format specifiers. Isolating error-containing elements is a tedious, trial-and-error practice with most software localization suites, but Lingobit Localizer automates this process.

How it works

It’s a usual situation when some translated string triggered crash in localized application and you need to find this defective translation. We could examine the code in debugger, but in that case we would need the source code and the help of developer. It is clear that calling for developer to fix a problem is the last resort during translation. Then there is the only way we can fix this: turning off each translation and checking if the application still crashes.

For large-scale projects, it would take huge amounts of time, but fortunately, there is a tool called Crash Finder that automates the task by accomplishing optimized search of translations that cause the crash. Crash Finder executes partly-translated application several times to detect the exact position of error-containing elements. For a project that contains several thousand elements, you need to run Crash Finder just about 10 times instead of thousands. So let’s use this convenient tool to find invalid translation.

Crash Finder can be used during any stage of localization process from localizability testing to final QA.

Learn more about Lingobit Localizer features