Starting with 2.7.6 Avidemux frequently crashes at conclusion of encoding

[Who]

Running MacOS Catalina (10.15.6) on a Mac Mini and about 75% of the time when Avidemux finishes encoding something it crashes.  The file it has created is fine, it's just an inconvenience to have to keep restarting it if you are doing several encodings in a row.  I have observed this in Avidemux 2.7.6 and 2.7.7, but never saw it in 2.7.4 or earlier.

[eumagga0x2a]

Could you please start Avidemux (the latest nightly, please) from the Terminal

Code Select Expand

/Applications/Avidemux_2.7.7/Contents/MacOS/Avidemux2.7 2>&1 | tee ~/admlog.txt
reproduce the crash, then compress and attach admlog.txt from your home directory to your reply?

[eumagga0x2a]

Maybe I should add that I don't experience such crashes with my private Avidemux builds for macOS. I cannot rule out that there is a problem with the official build, but also a problem related to a specific issue with the source video or with the choice or configuration of video filters is possible. The log would allow to assess the nature of the problem.

[eumagga0x2a]

Ping. If it turns out to be that this crash happens not simply due to a random transient build problem but is a result of a bug in the code, it would be a pity if the issue makes it into the next release, which is very likely, unless you help to assess the cause by providing requested information.

Many thanks in advance.

[Who]

I attempted to reply to this a few days ago and the forum software absolutely would not let me post for some reason.  Tonight it seems a bit more cooperative but I do not want to tempt the fates so I will keep this short.  I had done what you suggested but it produced a very long output file and since it is far too large to manually check to see what's in it, I do not wish to post it in its entirety.  However these were the last few lines prior to the crash:

Code Select Expand

Percent:96
Percent:96
Percent:96
Percent:96
[audioClock] Drift detectedNo accelerated IMDCT transform found
/Applications/Avidemux_2.7.7.app/Contents/MacOS/Avidemux2.7: line 4: 28467 Segmentation fault: 11  ./avidemux "$@"
Note that although it only shows that it was 96 percent complete, it did in fact finish encoding the file.  I have never seen it crash prior to actually finishing encoding the file.  Also, I have found that it seems a lot more likely to crash if I have turned off my display (I have a Mac Mini so the display is not built in) and walked away for a while.  The system is set to never go to sleep but there is a screen saver that kicks in after about five minutes of inactivity.  This is not to say that it has never crashed if I am actually using the computer when it finishes, but it seems a lot less likely to crash if I am actively interacting with the computer.

[eumagga0x2a]

I'm very sorry, but I need the entire file (please compress it (7z, zip, gzip or bzip2) prior to attaching it) as the excerpt you posted lacks crucial information.

Note that although it only shows that it was 96 percent complete, it did in fact finish encoding the file.

Did you check by examining the output?

I am sorry, I still haven't found time to test the official nightly, will try to do it today.

[eumagga0x2a]

I am sorry, I still haven't found time to test the official nightly, will try to do it today.

Nightly installed,

Code Select Expand

xattr -d com.apple.quarantine /Applications/Avidemux_2.7.7.app
executed, an 8 minutes long video encoded with x264, xvid4 and x265 (my MBP seemed to be about to melt, never heard the fan being that loud), no crashes so far.

[Who]

I'm very sorry, but I need the entire file (please compress it (7z, zip, gzip or bzip2) prior to attaching it) as the excerpt you posted lacks crucial information.

I'm just not comfortable posting that entire HUGE file in a public forum.  If that means you can't fix it then I'll just live with it.  Sorry.

Note that although it only shows that it was 96 percent complete, it did in fact finish encoding the file.

Did you check by examining the output?

Yes, the output was fine and the end of the file was there.  I have seen this several times and in no case has the file been incomplete.

I should also mentioned this has never happened on a short video, though that may just be coincidence.  It's always happened with a longer video (about 30 minutes or longer).  I always use x264 for encoding and always save as a mp4 file.  My computer's fan does seem to kick up a bit but not to any extreme (I hate noisy fans, so I would notice!).

If there is any specific piece of information you need from that file let me know and as long as it doesn't contain too detailed information about me or my system I'll post it, but I honestly doubt this forum software would even let me post that large of a file even if I wanted to, since the other day I could not even get it to accept a normal length post.

[eumagga0x2a]

I'm just not comfortable posting that entire HUGE file in a public forum.

Would it sufficient for you to replace the occurences of your user name and the path + name of the file loaded? You could also provide the file via PM or as link to an online storage e.g. Google Drive via PM.

If that means you can't fix it then I'll just live with it.

For now, it is just about trying to assess it. It is also very likely that the relevant info is available only in the crash report Apple tries to send to the mothership on every crash.

I should also mentioned this has never happened on a short video

This is bad as it makes it very unlikely that I will be ever able to reproduce it. As it is obviously not tied to a particular video, this might be actually a hardware problem.

I always use x264 for encoding and always save as a mp4 file.

This is a very important piece of the information. Do you experience the crash also with other encoders? Especially the VideoToolbox one and HEVC (x265) would be interesting.