Released 1.36.22, .23, .24 The Memory Remains

[iconnor]

# Changes since 1.36.21

- Make proportional zoom and movement work for AxisV2 API
- remove padding from ptz buttons making proportional zoom/pan not work right
- Fix memleak
- reduce debugging calls
- include reorder_queue_size setting in warning about out of order dts
- Sync up with c++ shm alignment to fix same size on 32bit
- improve warning about MaxImageBuffer size being smaller than keyframe interval
- Fix ever increasing duration in event list
- fix javascript console log about leaflet not being installed
- Fix event listing for filter involving AlarmedZone rule.
- Fix logic inversion causing Filters involving DiskPercent rules to still hit the database
- Fix too much logging about finding locked packets
- Fix segfault when audio stream is present but not being recorded
- when a new auth hash is generated, don't reload the image stream, just update the global var to be used if the image stream breaks.

# Changes since 1.36.22

- Fix failed build
- set timezone when initializing IntlDateFormatter

# Changes since 1.36.23

- fixes failure to build due to missing ffmpeg include in zm_packet.h
- add -x option to zmu to get monitor triggered status.
- fix deadlock when doing logrot when analysis is waiting for decode. We do this by notifying each packet in packetqueue::stop.
- [Revert "Sync up with c++ shm alignment to fix same size of 32bit"](https://github.com/ZoneMinder/zoneminde ... f3ef4c4d18)
- Fix hang due to not increasing iterator for audio packets.
- [Fix memleak due to not deleting okpt in VideoStore destructor](https://github.com/ZoneMinder/zoneminde ... 1d9bd333b8)

1.36.24
Full Changelog

[lightguy48]

I was running updates on my machine and happened to get the .24 release and now every one of my cameras is logging keyframe / max buffer errors.

I'm well above the keyframe interval and never had a problem before the update.

1344 WAR Did not find a second keyframe in the packet queue. It may be that the Max Image Buffer setting is lower than the keyframe interval. We need it to be greater than the keyframe interval.

Some kind of bug? I do use camera passthrough and movflags=faststart I haven't tried disabling the faststart yet to see if it makes any difference.