Dahua IPC produce corrupted images

[d5775927]

I have a few Dahua IPCs, I have a program that pushed events from the camera to Telegram.
Sometimes I see the image send fails (telegram says the uploaded image is corrupted).
Also, when opening snapshots in Firefox browser I see this message in Firefox log:

Corrupt JPEG data: 608 extraneous bytes before marker 0xfe

I'm not going to update my camera firmware to fix that (since this doesn't occur very frequently, I think mainly happens in SceneChange event or ManualSnapshot).
Just wanted Dahua to fix this in some future firmware or IPCs.

AFAIK, the error message means that the JPEG image produced by the camera is not a valid JPEG, in some cases image viewer are able to still show the image and in some cases the image too corrupted to be displayed.

 

[TonyR]

Is more than one camera producing the "corrupted" images?

When the URL for a snapshot is sent directly to the camera using a browser is the returned image ever corrupted also?

 

[d5775927]

Is more than one camera producing the "corrupted" images?

When the URL for a snapshot is sent directly to the camera using a browser is the returned image ever corrupted also?

No. But I don't use the snapshot button in the browser much.
I use the Dahua API - sending request directly to the IPC:

http://<IPC-IP>/cgi-bin/snapManager.cgi?action=attachFileProc&Flags[0]=Event&Events=[All]&heartbeat=5

The issue reproduces on multiple IPCs, different models:
1 x 2431T - happens when an IVS rule triggered (happens very rarely)
2 x 5442ZE - happens on both - upon SceneChange event (when drastic light change occur - like sunset/sunrise)
Looking back since November these are the dates in which I had a corrupted image:

Nov 15 16:59:45
Nov 16 05:43:27
Nov 17 05:50:09
Nov 17 05:50:10
Nov 17 05:50:11
Nov 17 05:50:12
Nov 17 05:50:14
Nov 22 17:54:02
Nov 22 17:54:02
Nov 22 17:54:03
Nov 22 17:54:04
Nov 22 17:54:10
Nov 26 22:51:43
Nov 27 06:02:40
Nov 27 16:59:45
Nov 28 06:00:32

Not using WIFI, using cat5e cable.
I don't have connectivity issues (my guess is that this is a software/firmware issue)