News:

--

Main Menu

"unhandled action 4" when closing window

Started by karl, May 05, 2012, 03:09:40 PM

Previous topic - Next topic

karl

When I opened a file, scrolled through its content, then close the avidemux26 window, I get the following error:

  [HandleAction]  ************ EXIT **************
unhandled action 4
Saving crash file to /home/test/.avidemux6/crash.py


The immediate reason for this is that the "switch (action)" statement in avidemux/common/gui_main.cpp:328 has no "case" statement for "ACT_EXIT".

I tried to copy & paste a similar case from earlier in the same source file:

   case ACT_EXIT:
   UI_closeGui();
      break;


Alas, this causes avidemux (instead of crashing) to wait indefinitely after printing

[renderDestroy]  Cleaning up Render
  [GUI_XvEnd]  [Xvideo] Releasing Xv Port

at this function:

#0  0x00007f52d6205d70 in __pause_nocancel () from /lib64/libpthread.so.0
#1  0x00007f52d61fff9b in __pthread_mutex_lock_full () from /lib64/libpthread.so.0
#2  0x0000003997a0902c in xcb_writev () from /usr/lib64/libxcb.so.1
#3  0x0000003997e4d41a in _XSend () from /usr/lib64/libX11.so.6
#4  0x0000003997e3ab2b in XQueryExtension () from /usr/lib64/libX11.so.6
#5  0x0000003997e2efd2 in XInitExtension () from /usr/lib64/libX11.so.6
#6  0x000000399820e422 in XextAddDisplay () from /usr/lib64/libXext.so.6
#7  0x0000003994201746 in XvUngrabPort () from /usr/lib64/libXv.so.1
#8  0x00007f52d5acd4f5 in XvRender::stop() () from /usr/local/app/avidemux26/lib/libADM_render6_qt4.so
#9  0x00007f52d5acc72b in renderDestroy() () from /usr/local/app/avidemux26/lib/libADM_render6_qt4.so
#10 0x0000000000435d0a in onexit() ()
#11 0x00007f52d4782d92 in exit () from /lib64/libc.so.6
#12 0x00007f52d476bce4 in __libc_start_main () from /lib64/libc.so.6
#13 0x0000000000430059 in _start ()


This may be related to the "xcb_io.c:445: _XReply: Assertion `!dpy->xcb->reply_data' failed." bug I reported earlier: If I choose "quit" from the menu instead of closing the window, I get this "Assertion `!dpy->xcb->reply_data' failed." crash instead of the above mentioned symptoms.
(But notice how for this bug report, vdpau was not at all involved, as I disabled it in the preferences.)

karl

This issue has already been solved by Mean's recent commit fixing the "xcb_io.c:445: _XReply: Assertion `!dpy->xcb->reply_data' failed." issue. Thanks!