<html><head><style>p{margin-top:0px;margin-bottom:0px;}</style></head><body><div style="font-size:13px; font-family:NanumGothic,나눔고딕,sans-serif;"><div>Hi.</div><div></div><div>Thanks to rapidly support.</div><div>I applied patch you sent to me to latest x264 branch and tried to encode few 4K contents which make seg fault problem.</div><div>And I finally got normal encoded videos.</div><div></div><div>When I saw patch, it changes variable type of slicetype_path_cost, int(32) to uint64.</div><div>It means that when calculate slicetype_path_cost at 4K video contents, this may occurs overflow, right?</div><div>But I wonder why it was encoded properly when I changed the number of threads.</div><div></div><div>Do I apply your patch onto latest x264 and can I use it?</div><div>I wish you commit this patch to x264 branch because I use pure libx264, without any changes.</div><div></div><div>Once again, thank you for your support.</div><div></div><div>Regards.</div><div><div style="line-height: 16px; font-family: 나눔고딕, NanumGothic, 돋움, dotum, 굴림, Gulim, AppleGothic, sans-serif;"></div></div></div></body></html><table style='display:none'><tr><td><img src="https://ack.mail.navercorp.com/readReceipt/notify/?img=mfKmKxgqaxKXK4UYaqumaxb9FAv%2Fax3oMxuZKxCop6poFq2raxvXFqC4KEIo%2BrkSKAK5W49vpSl51zlqDBFdp6d5MreRhoR%2FKoMd7630%2B4kntHpGpzkTWzJ574eZpm%3D%3D.gif" border="0"/></td></tr></table>