Avidemux 2.7.9 210731 audio and video won't stay in sync

[Who]

Well I tried OpenGL and encoded one video with it and it did not crash, but then I came across a bug that was so bad that I could not continue to use this version, and had to revert to a Time Machine backup of an earlier version (the first time a bug in Avidemux has ever been so bad that I have felt been forced to do this).  I posted the details in the thread at https://avidemux.org/smif/index.php/topic,19447.150.html

So unfortunately I will not be able to give you any more feedback about this version because it is no longer on my system, having been overwritten by the version from the Time Machine backup.  If there had been any easy way to work around that bug I would have done so, but there wasn't that I could find.

[eumagga0x2a]

As long as the A marker is equal zero, the bug (now fixed) doesn't hit. I'll request a refresh of nightly builds.

[Who]

Using OpenGL it did crash on me today just after saving the encoded file.  That admlog.txt you wanted is a very long file and on this forum you are limited to PM's of 20,000 bytes, so I sent you two PM's containing approximately the first and last 20,000 bytes of that file.  I hope that is enough.

[eumagga0x2a]

Thanks, the main finding is that whatever causes the crash doesn't leave traces in stdout and stderr output of the killed application (i.e. Avidemux). This means it will be necessary to run Avidemux in Terminal to get a clue what happens (or you provide the crash report from the Console). The log file only hints that the crash is not an orderly assert failure but a sudden death from external causes.

[Who]

I have run Avidemux in the terminal before and the output from that wasn't at all helpful.  I sent you a PM with the first 20,000 or so bytes of the crash log, if there is a clue anywhere it may be there but I don't know if it will mean anything to you.

[eumagga0x2a]

I have run Avidemux in the terminal before and the output from that wasn't at all helpful.

This was due to my request to redirect the output which unexpectedly for me re-enabled writing debug messages to /tmp/admlog.txt which I tried to avoid in the first place.

I sent you a PM with the first 20,000 or so bytes of the crash log

Thank you, this was by far the best solution.