Assigning to the concern owner from Find it. Below are the results --
The result is a list of CLs that change the crashed files. 

Author: tsepez
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/833619b4441915c7c55085d44b3221eaef0d9800
Time: Wed Dec 07 09:21:17 2016 -0800
File fpdfview.cpp is changed in this cl (and is part of stack frame #6, "FPDF_LoadPage")
Minimum distance from crash line to modified line: 73. (file: fpdfview.cpp, crashed on: 624, modified: 551). 

Author: caryclark
Project: chromium-pdfium
Changelist: https://pdfium.googlesource.com/pdfium.git/+/8f875507a986d10335e40a5f7c1679aff9770d0a
Time: Tue Dec 06 13:49:34 2016 -0800
File fpdfview.cpp is changed in this cl (and is part of stack frame #6, "FPDF_LoadPage")
Minimum distance from crash line to modified line: 86. (file: fpdfview.cpp, crashed on: 637, modified: 723).

@tsepez -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

ClusterFuzz has detected this issue as fixed in range 440242:440280.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6003104723238912

Fuzzer: ochang_search_index_mutator
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Float-cast-overflow
Crash Address: 
Crash State:
  CPDF_Color::GetRGB
  CPDF_ColorState::SetColor
  CPDF_StreamContentParser::Handle_SetColorPS_Stroke
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=435261:438085
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=440242:440280

Minimized Testcase (281.73 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96pLd2CRmNHFkqWj41fE39MJOBR6xLJ45AWxQ2YVChc4jlSmmO2U3D_3LqVgleRb47Aw4hsj-qrkyzQEUvlvzeBv0sGXC33PzAS-S4zlC0Q4xDV5jcpgzjIfQX3E2FjL8kdOtOYaL3gLUQPi-wDiDrsKnEc7qqkHnm4t9-FRgyu6q9tn8k?testcase_id=6003104723238912

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6003104723238912 is verified as fixed, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.