[Fontconfig-bugs] [Bug 103237] FcCacheOffsetsValid() couldn't detect broken cache file

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=103237

--- Comment #3 from Youngbok Shin <youngb.shin at samsung.com> ---
Created attachment 134812
  --> https://bugs.freedesktop.org/attachment.cgi?id=134812&action=edit
Normal (Proper) cache file.

I agree with your opinion.
We need to figure out how/why this broken cache was generated.
It should be fixed. And it will be great solution.
But, unfortunately, we couldn't figure out how it was generated.
This broken cache file was found from release binary of our product.
But, it was not created by any processes and fc-cache from engineer binary.

----------------
I will attach proper cache file. You can see this file is longer than the
broken one.
The broken one looks like a cache writer is dead while it is being written.

We assumed that it could be happened if device is turned off (power off) while
fontconfig is writing the cache. But, not proved.

----------------
Anyway, I'll ask product engineer to test product after applying your patch.
Thank you!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20171012/b616bae3/attachment.html>