JPEG related crashes

Lord_D said on 01/11/2018


Several recent versions of pingo crash when processing some JPEG files with -s3 and higher.



Cédric Louvrier said on 01/11/2017

0.93b seems to work, i can not reproduce the crash with the provided sample

Lord_D said on 01/12/2018

pingo 0.93b x64

OS: Windows 7 Pro SP1 x64

CPU: AMD Phenom II X6 1100T

Problem signature:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	pingo.exe
  Application Version:
  Application Timestamp:	5a4d0b29
  Fault Module Name:	pingo.exe
  Fault Module Version:
  Fault Module Timestamp:	5a4d0b29
  Exception Code:	c000001d
  Exception Offset:	000000000008b32c
  OS Version:	6.1.7601.
  Locale ID:	1049
  Additional Information 1:	cfc0
  Additional Information 2:	cfc0f971908f27771e064aa3d1d484f4
  Additional Information 3:	1625
  Additional Information 4:	162501d1028e052a02a97b7f5d498814

32-bit pingo does not crash. The problem can be related to the lack of support for some instruction sets, such as SSE4 in the AMD CPU.

Is there anything else I can do to help you debug this problem?

Cédric Louvrier said on 01/12/2017

can you try 0.93c?

Lord_D said on 01/13/2018

0.93c does not crash. Thank you!

I decided not to create a new topic.

I noticed that pingo sometimes produces a file a few bytes larger than mozjpeg one. If you view the file in HEX mode, you can see something like an encoder name in the very beginning. All files are processed with options "-s8 -strip=3".

Also pay attention to the file named "error.jpg". For some reason pingo refuses to process it.

Cédric Louvrier said on 01/13/2017

0.93d should fix this. "error.jpg" is read-only, so pingo could write a tmp file and ignore savings if you do not change the attribute

Lord_D said on 01/15/2018

Oh, I forgot about the read-only attribute. Thank you very much!

comment this