Author Topic: Avidemux 2.7.0 is unworkable :(  (Read 1092 times)

Jan Gruuthuse

  • Hero Member
  • *****
  • Posts: 5671
Re: Avidemux 2.7.0 is unworkable :(
« Reply #15 on: September 16, 2017, 02:07:02 PM »
Test avidemux 32-bit and report that.
Developer(s) will  hopefully pick up on his thread and reply.

YPetr

  • Newbie
  • *
  • Posts: 7
Re: Avidemux 2.7.0 is unworkable :(
« Reply #16 on: September 16, 2017, 02:21:21 PM »
Ok, I'll do it.

eumagga0x2a

  • Hero Member
  • *****
  • Posts: 1534
Re: Avidemux 2.7.0 is unworkable :(
« Reply #17 on: September 16, 2017, 03:42:33 PM »
While I am unable to reproduce the issue on Linux, am I right that after pressing the "Previous Frame" button 2-3 times in a rapid sequence a sort of "autoscroll" begins, which finally results in a crash? This kind of a bug, likely attributable to the Qt toolkit, was workarounded in 2.7.0 for the navigation slider by letting the slider handle immediately jump to the click position also on Linux and Windows (it was always this way on Mac). I never tried (and now didn't succeed) to reproduce the issue using the navigation buttons instead of mouse.

eumagga0x2a

  • Hero Member
  • *****
  • Posts: 1534
Re: Avidemux 2.7.0 is unworkable :(
« Reply #18 on: September 16, 2017, 04:29:04 PM »
Please reproduce the crash with the latest nightly and attach a compressed admlog.txt from %localappdata%\avidemux together with precise steps to reproduce the issue.

eumagga0x2a

  • Hero Member
  • *****
  • Posts: 1534
Re: Avidemux 2.7.0 is unworkable :(
« Reply #19 on: September 20, 2017, 08:24:12 PM »
Finally got a chance to test on a German Windows 7 SP1 with my own win64 build from the current git master. I cannot reproduce the issue, no matter how hard I try. Unless you provide steps which allow to reproduce the issue, I attribute it to your system.

AQUAR

  • Hero Member
  • *****
  • Posts: 1037
Re: Avidemux 2.7.0 is unworkable :(
« Reply #20 on: September 21, 2017, 12:49:10 AM »
If the OP looks in his windows system "event viewer" he will note that the crashed ADM is pointing to some faulting module.
ADM log points to NTDLL.DLL and that should be verified by the "event viewer".

If its a system module - a good first step would be to run System File Checker to repair any corrupted system files.
That said the OP has this issue on other PC's as well, so who knows (it doesn't happen on my English OS). 

« Last Edit: September 21, 2017, 01:57:06 AM by AQUAR »