Make Font Table construction resilient to lack of font pathname

If we were unable to retrieve a path for a font registered in the system
font collection, continue with the next font in the system font
collection, instead of hitting the assertion. Speculative fix for such
cases seen in the wild, unable to reproduce locally as it probably is
hit for corrupt fonts or an invalid font registration in the registry.

Bug: 922183
Change-Id: Ic071cee9a16ef0cb3a6fe095474348e437d65459
Reviewed-by: Koji Ishii <>
Commit-Queue: Dominik Röttsches <>
Cr-Commit-Position: refs/heads/master@{#623193}
1 file changed