Crash Finder

A translation can make the localized application crash, for example a format string with a missing or extra placeholder or a string that overflows a buffer. When validation does not show the cause, Crash Finder finds the translation that causes the crash. Crash Finder is available in Enterprise.

How it works

Crash Finder builds test versions of the localized file with only part of the translations applied. You run each version and answer whether it crashed. Every answer halves the suspects, until Crash Finder finds the translation that causes the crash. For example, about ten runs are enough to check a thousand translations.

Run Crash Finder

  1. Choose Project > Crash Finder to search the whole project, or select a file in the Navigation pane and choose Additional Actions > Crash Finder in its shortcut menu to search this file.

  2. Check the command, arguments, and working directory that start the application, and click OK. They are the same as for Run Localized; see Run Parameters.

  3. Crash Finder starts each test version. Repeat what made the application crash and answer Did the program crash? with Yes or No.

When the search is finished, the Output panel shows the translation that causes the problem. Double-click it to go to the item, correct the translation, and create the localized files again.

See also Localizability Testing and How to check translations.