segmentation fault during video export

Bug #1195050 reported by Don Harter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenShot Video Editor
New
Undecided
Unassigned

Bug Description

openshot-1.4.3
run from compiled code
suse 12.3

python-mlt-0.8.8-40.1.x86_64
libmlt4-modules-0.7.8-2.8.1.x86_64
libmlt4-0.7.8-2.8.1.x86_64
libmlt4-data-0.7.8-2.8.1.noarch
libmlt5-modules-0.8.8-40.1.x86_64
libmlt++3-0.8.8-40.1.x86_64
libmlt5-0.8.8-40.1.x86_64
libmlt5-data-0.8.8-8.1.noarch

libavcodec54-1.0.6-1.1.x86_64
libavc1394-devel-32bit-0.5.4-8.1.2.x86_64
libavc1394-0-0.5.4-8.1.2.x86_64
libavc1394-devel-0.5.4-8.1.2.x86_64
libavcodec54-32bit-1.0.6-1.1.x86_64
libavc1394-0-32bit-0.5.4-8.1.2.x86_64
libavcodec52-0.7.15-1.2.x86_64

gstreamer-0_10-plugins-ffmpeg-0.10.13-2000.7.x86_64
ffmpeg-debuginfo-1.0.6-1.1.x86_64
ffmpeg-debugsource-1.0.6-1.1.x86_64
ffmpeg-1.0.6-1.1.x86_64

 - alsa
  - oss
  - sdl
...
state saved
project state modified
state saved
NEW SDL CONSUMER
on_mnuMakeMovie1_activate called with self.GtkImageMenuItem
on_tlbMakeMovie_clicked called with self.GtkImageMenuItem
on_cboExportType_changed
on_cboUploadServices_changed
on_cboProjectType_changed
on_cboExportTo_changed
on_cboProjectType_changed
on_btnExportVideo_clicked
NEW SDL CONSUMER
[ac3_fixed @ 0x7f0ab42db240] channel_layout not specified
[ac3_fixed @ 0x7f0ab42db240] No channel layout specified. The encoder will guess the layout, but it might be incorrect.
[h264 @ 0x7f0ab42c6c20] Encoder did not produce proper pts, making some up.
sys:1: Warning: g_main_context_push_thread_default: assertion `acquired_context' failed
Segmentation fault

Revision history for this message
Don Harter (harterc2) wrote :
Revision history for this message
Don Harter (harterc2) wrote :

This crashes for every format that I have tried.

Revision history for this message
Olivier Girard (eolinwen) wrote : Re: [Openshot.bugs] [Bug 1195050] Re: segmentation fault during video export

I don't know where is the problem as you are using an Opensuse (and not me)
but I note that you have still some part from MLT in the version 0.7.8. And
that, it is not normal.
Could you use H264 and mp3 with your version of ffmpeg ?
Take a look in the Preferences, if you have this codecs or run and
copy/paste openshot in a console.

2013/6/28 Don Harter <email address hidden>

> This crashes for every format that I have tried.
>
> --
> You received this bug notification because you are a member of OpenShot
> Bugs, which is subscribed to OpenShot Video Editor.
> https://bugs.launchpad.net/bugs/1195050
>
> Title:
> segmentation fault during video export
>
> Status in OpenShot Video Editor:
> New
>
> Bug description:
> openshot-1.4.3
> run from compiled code
> suse 12.3
>
>
> python-mlt-0.8.8-40.1.x86_64
> libmlt4-modules-0.7.8-2.8.1.x86_64
> libmlt4-0.7.8-2.8.1.x86_64
> libmlt4-data-0.7.8-2.8.1.noarch
> libmlt5-modules-0.8.8-40.1.x86_64
> libmlt++3-0.8.8-40.1.x86_64
> libmlt5-0.8.8-40.1.x86_64
> libmlt5-data-0.8.8-8.1.noarch
>
> libavcodec54-1.0.6-1.1.x86_64
> libavc1394-devel-32bit-0.5.4-8.1.2.x86_64
> libavc1394-0-0.5.4-8.1.2.x86_64
> libavc1394-devel-0.5.4-8.1.2.x86_64
> libavcodec54-32bit-1.0.6-1.1.x86_64
> libavc1394-0-32bit-0.5.4-8.1.2.x86_64
> libavcodec52-0.7.15-1.2.x86_64
>
>
> gstreamer-0_10-plugins-ffmpeg-0.10.13-2000.7.x86_64
> ffmpeg-debuginfo-1.0.6-1.1.x86_64
> ffmpeg-debugsource-1.0.6-1.1.x86_64
> ffmpeg-1.0.6-1.1.x86_64
>
>
>
> - alsa
> - oss
> - sdl
> ...
> state saved
> project state modified
> state saved
> NEW SDL CONSUMER
> on_mnuMakeMovie1_activate called with self.GtkImageMenuItem
> on_tlbMakeMovie_clicked called with self.GtkImageMenuItem
> on_cboExportType_changed
> on_cboUploadServices_changed
> on_cboProjectType_changed
> on_cboExportTo_changed
> on_cboProjectType_changed
> on_btnExportVideo_clicked
> NEW SDL CONSUMER
> [ac3_fixed @ 0x7f0ab42db240] channel_layout not specified
> [ac3_fixed @ 0x7f0ab42db240] No channel layout specified. The encoder
> will guess the layout, but it might be incorrect.
> [h264 @ 0x7f0ab42c6c20] Encoder did not produce proper pts, making some
> up.
> sys:1: Warning: g_main_context_push_thread_default: assertion
> `acquired_context' failed
> Segmentation fault
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openshot/+bug/1195050/+subscriptions
>
> --
> Mailing list: https://launchpad.net/~openshot.bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openshot.bugs
> More help : https://help.launchpad.net/ListHelp
>

--
Olivier
Cenwen un elfe sur la banquise/ an elve on the ice
Mon blog perso sur le multimédia, Ubuntu, Linux et OpenShot :
http://linuxevolution.wordpress.com/
Le forum d'Openshot où vous me trouverez : http://openshotusers.com/
http://openshotusers.com/forum/index.php
Nothing is lost until the last second.
The family motto : When we want, we can.
Astuces, Actualités, Logiciels, bref sur tout ce que je ne fais d'articles
dessus Google+ <https://plus.google.com/u/0/111472725110173916234/posts>

Revision history for this message
Olivier Girard (eolinwen) wrote :
Download full text (3.9 KiB)

If your problen is still present, run openshot using gdb and put the output
from the terminal here.
Thxs.

2013/6/28 <email address hidden> <email address hidden>

> I don't know where is the problem as you are using an Opensuse (and not
> me) but I note that you have still some part from MLT in the version 0.7.8.
> And that, it is not normal.
> Could you use H264 and mp3 with your version of ffmpeg ?
> Take a look in the Preferences, if you have this codecs or run and
> copy/paste openshot in a console.
>
>
> 2013/6/28 Don Harter <email address hidden>
>
>> This crashes for every format that I have tried.
>>
>> --
>> You received this bug notification because you are a member of OpenShot
>> Bugs, which is subscribed to OpenShot Video Editor.
>> https://bugs.launchpad.net/bugs/1195050
>>
>> Title:
>> segmentation fault during video export
>>
>> Status in OpenShot Video Editor:
>> New
>>
>> Bug description:
>> openshot-1.4.3
>> run from compiled code
>> suse 12.3
>>
>>
>> python-mlt-0.8.8-40.1.x86_64
>> libmlt4-modules-0.7.8-2.8.1.x86_64
>> libmlt4-0.7.8-2.8.1.x86_64
>> libmlt4-data-0.7.8-2.8.1.noarch
>> libmlt5-modules-0.8.8-40.1.x86_64
>> libmlt++3-0.8.8-40.1.x86_64
>> libmlt5-0.8.8-40.1.x86_64
>> libmlt5-data-0.8.8-8.1.noarch
>>
>> libavcodec54-1.0.6-1.1.x86_64
>> libavc1394-devel-32bit-0.5.4-8.1.2.x86_64
>> libavc1394-0-0.5.4-8.1.2.x86_64
>> libavc1394-devel-0.5.4-8.1.2.x86_64
>> libavcodec54-32bit-1.0.6-1.1.x86_64
>> libavc1394-0-32bit-0.5.4-8.1.2.x86_64
>> libavcodec52-0.7.15-1.2.x86_64
>>
>>
>> gstreamer-0_10-plugins-ffmpeg-0.10.13-2000.7.x86_64
>> ffmpeg-debuginfo-1.0.6-1.1.x86_64
>> ffmpeg-debugsource-1.0.6-1.1.x86_64
>> ffmpeg-1.0.6-1.1.x86_64
>>
>>
>>
>> - alsa
>> - oss
>> - sdl
>> ...
>> state saved
>> project state modified
>> state saved
>> NEW SDL CONSUMER
>> on_mnuMakeMovie1_activate called with self.GtkImageMenuItem
>> on_tlbMakeMovie_clicked called with self.GtkImageMenuItem
>> on_cboExportType_changed
>> on_cboUploadServices_changed
>> on_cboProjectType_changed
>> on_cboExportTo_changed
>> on_cboProjectType_changed
>> on_btnExportVideo_clicked
>> NEW SDL CONSUMER
>> [ac3_fixed @ 0x7f0ab42db240] channel_layout not specified
>> [ac3_fixed @ 0x7f0ab42db240] No channel layout specified. The encoder
>> will guess the layout, but it might be incorrect.
>> [h264 @ 0x7f0ab42c6c20] Encoder did not produce proper pts, making some
>> up.
>> sys:1: Warning: g_main_context_push_thread_default: assertion
>> `acquired_context' failed
>> Segmentation fault
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/openshot/+bug/1195050/+subscriptions
>>
>> --
>> Mailing list: https://launchpad.net/~openshot.bugs
>> Post to : <email address hidden>
>> Unsubscribe : https://launchpad.net/~openshot.bugs
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Olivier
> Cenwen un elfe sur la banquise/ an elve on the ice
> Mon blog perso sur le multimédia, Ubuntu, Linux et OpenShot :
> http://linuxevolution.wordpress.com/
> Le forum d'Openshot où vous me trouverez : http://openshotusers.com/
> http://openshot...

Read more...

Revision history for this message
Don Harter (harterc2) wrote :

I tried previously to run gdb , but it doesn't recognize the python openshot as a binary file. Some of my files come from packman. I don't have mp3 as an option with h264 in openshot. Perhaps my version off fmpeg does not have it. I looked at similar bug reports and saw that different version of libavc and ffmpeg can cause problems. Also that one is the subset of anoher. I will try to install a different version of ffmepg and/or maybe uninstall libavc if that is a subset of the full version of ffmpeg. mp may have been disabled by suse because of licensing problems.

Revision history for this message
Don Harter (harterc2) wrote :

I found that I had a suse version of ffmpeg installed. I replaced that with the packman version. I still get this problem:
- sdl
...
state saved
project state modified
state saved
NEW SDL CONSUMER
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
on_mnuMakeMovie1_activate called with self.GtkImageMenuItem
on_tlbMakeMovie_clicked called with self.GtkImageMenuItem
on_cboExportType_changed
on_cboUploadServices_changed
on_cboProjectType_changed
on_cboExportTo_changed
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
on_btnExportVideo_clicked
NEW SDL CONSUMER
[ac3_fixed @ 0x7f58742db240] channel_layout not specified
[ac3_fixed @ 0x7f58742db240] No channel layout specified. The encoder will guess the layout, but it might be incorrect.
[h264 @ 0x7f58742c6c20] Encoder did not produce proper pts, making some up.
sys:1: Warning: g_main_context_push_thread_default: assertion `acquired_context' failed
Segmentation fault

I see a choice for mp3 format but it is listed as a video format in the drop down box menu.

Revision history for this message
Don Harter (harterc2) wrote :

I ttried with mp2 as the audio format. It also crashed and here is the output from the konsole:
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
NEW SDL CONSUMER
[mp2 @ 0x7f92b82db1a0] channel_layout not specified
[h264 @ 0x7f92b82c6c20] Encoder did not produce proper pts, making some up.
sys:1: Warning: g_main_context_push_thread_default: assertion `acquired_context' failed
Segmentation fault

Perhaps I need ot remove libavc packages since they are contained in ffmpeg??

Revision history for this message
Don Harter (harterc2) wrote :

I am in the process of building my own rpms from the latest source files. I can see that there is a problem with the spec file for mlt. It does not recognize qt4 properly. The test looks for qt4 files in the wrong directory for suse kde.
Does anyone know what versions of ffmeg and mlt work with the latest stable open shot?

Revision history for this message
Olivier Girard (eolinwen) wrote :
Download full text (3.9 KiB)

Effectively you could have different versions of ffmpeg.

You seems to have a problem with alsa.
Hum you could choice between alsa and pulseaudio but :
like I have reformated my HD and turn on my SSD, I don't keep the link for
dependencies.
Secondly, I am not sure that the same for Suse.

If I could give you an advice, you should take a look at our forum (
http://www.openshotusers.com/forum) and search the topic about dependencies
for the version 1.4.x in the section installation (if my memory is still
good). If this one is always still good, you 'll find normally for
Opensuse, mandriva, Ubuntu, Debian, Slackware,................

If you want to create your own rpm (for MLT) good luck.

2013/7/1 Don Harter <email address hidden>

> I am in the process of building my own rpms from the latest source files.
> I can see that there is a problem with the spec file for mlt. It does not
> recognize qt4 properly. The test looks for qt4 files in the wrong
> directory for suse kde.
> Does anyone know what versions of ffmeg and mlt work with the latest
> stable open shot?
>
> ** Attachment added: "ffmpeg.spec"
>
> https://bugs.launchpad.net/openshot/+bug/1195050/+attachment/3720473/+files/ffmpeg.spec
>
> --
> You received this bug notification because you are a member of OpenShot
> Bugs, which is subscribed to OpenShot Video Editor.
> https://bugs.launchpad.net/bugs/1195050
>
> Title:
> segmentation fault during video export
>
> Status in OpenShot Video Editor:
> New
>
> Bug description:
> openshot-1.4.3
> run from compiled code
> suse 12.3
>
>
> python-mlt-0.8.8-40.1.x86_64
> libmlt4-modules-0.7.8-2.8.1.x86_64
> libmlt4-0.7.8-2.8.1.x86_64
> libmlt4-data-0.7.8-2.8.1.noarch
> libmlt5-modules-0.8.8-40.1.x86_64
> libmlt++3-0.8.8-40.1.x86_64
> libmlt5-0.8.8-40.1.x86_64
> libmlt5-data-0.8.8-8.1.noarch
>
> libavcodec54-1.0.6-1.1.x86_64
> libavc1394-devel-32bit-0.5.4-8.1.2.x86_64
> libavc1394-0-0.5.4-8.1.2.x86_64
> libavc1394-devel-0.5.4-8.1.2.x86_64
> libavcodec54-32bit-1.0.6-1.1.x86_64
> libavc1394-0-32bit-0.5.4-8.1.2.x86_64
> libavcodec52-0.7.15-1.2.x86_64
>
>
> gstreamer-0_10-plugins-ffmpeg-0.10.13-2000.7.x86_64
> ffmpeg-debuginfo-1.0.6-1.1.x86_64
> ffmpeg-debugsource-1.0.6-1.1.x86_64
> ffmpeg-1.0.6-1.1.x86_64
>
>
>
> - alsa
> - oss
> - sdl
> ...
> state saved
> project state modified
> state saved
> NEW SDL CONSUMER
> on_mnuMakeMovie1_activate called with self.GtkImageMenuItem
> on_tlbMakeMovie_clicked called with self.GtkImageMenuItem
> on_cboExportType_changed
> on_cboUploadServices_changed
> on_cboProjectType_changed
> on_cboExportTo_changed
> on_cboProjectType_changed
> on_btnExportVideo_clicked
> NEW SDL CONSUMER
> [ac3_fixed @ 0x7f0ab42db240] channel_layout not specified
> [ac3_fixed @ 0x7f0ab42db240] No channel layout specified. The encoder
> will guess the layout, but it might be incorrect.
> [h264 @ 0x7f0ab42c6c20] Encoder did not produce proper pts, making some
> up.
> sys:1: Warning: g_main_context_push_thread_default: assertion
> `acquired_context' failed
> Segmentation fault
>
> To manage notifications about this bug go to:
> https://bugs.launchpa...

Read more...

Revision history for this message
Don Harter (harterc2) wrote :

I built some rpms for mlt using mlt-x0.9.0.
No change it crashed still.
From the terminal:
ALSA lib pcm.c:7339:(snd_pcm_recover) underrun occurred
on_btnExportVideo_clicked
NEW SDL CONSUMER
[ac3_fixed @ 0x7fb9442cea40] Channel layout not specified
[ac3_fixed @ 0x7fb9442cea40] No channel layout specified. The encoder will guess the layout, but it might be incorrect.
[h264 @ 0x7fb9442c6c20] Encoder did not produce proper pts, making some up.
WARNING: QApplication was not created in the main() thread.
sys:1: Warning: g_main_context_push_thread_default: assertion `acquired_context' failed
Segmentation fault

So upgrading to ffmpeg-1.2.1 and mlt-0.9.0 doesn't seem to fix the problem.

Revision history for this message
Don Harter (harterc2) wrote :

I typed python debug.py as a non-root user and go this output.
-----------------------------------------------------------
OpenShot Debug File 0.0.2 - 2013-07-02 16:14:31.573740
-----------------------------------------------------------
This file contains a list of installed packages related to OpenShot,
locations of files, and a list of shared libraries used by python-mlt.

-----------------------------------------------------------
Distribution Version Info
-----------------------------------------------------------
LSB Version: core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch
Distributor ID: SUSE LINUX
Description: openSUSE 12.2 (x86_64)
Release: 12.2
Codename: Mantis

Traceback (most recent call last):
  File "debug.py", line 45, in <module>
    process = subprocess.Popen(["dpkg","-l","openshot", "libmlt1", "libmlt2", "python-mlt", "python-mlt2", "openshot-mlt"], stdout=subprocess.PIPE, stdin=subprocess.PIPE, stderr=subprocess.STDOUT)
  File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

From looking at messages it seems others have fixed segfault problems by moving back to mlt-0.7

Revision history for this message
Don Harter (harterc2) wrote :

I read in the forums how to run gdb.
Here is what is on the console and a bt:
New Thread 0x7fffbf015700 (LWP 13739)]
[New Thread 0x7fffa52ef700 (LWP 13740)]
[mp2 @ 0x7fff942ce9a0] Channel layout not specified
[h264 @ 0x7fff942c6c20] Encoder did not produce proper pts, making some up.
[New Thread 0x7fff9f7fe700 (LWP 13742)]
WARNING: QApplication was not created in the main() thread.
sys:1: Warning: g_main_context_push_thread_default: assertion `acquired_context' failed

Program received signal SIGSEGV, Segmentation fault.
0x00007fffd38c1a43 in x11EventSourceCheck (s=0x7fffb4068200) at kernel/qguieventdispatcher_glib.cpp:85
85 kernel/qguieventdispatcher_glib.cpp: No such file or directory.
(gdb) bt
#0 0x00007fffd38c1a43 in x11EventSourceCheck (s=0x7fffb4068200) at kernel/qguieventdispatcher_glib.cpp:85
#1 0x00007ffff66b819b in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#2 0x00007ffff66b8622 in ?? () from /usr/lib64/libglib-2.0.so.0
#3 0x00007ffff66b8ae2 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#4 0x00007ffff45740d7 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0
#5 0x00007ffff4c1d508 in ?? () from /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/_gtk.so
#6 0x00007ffff7aef6aa in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#7 0x00007ffff7af235d in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#8 0x00007ffff7af235d in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#9 0x00007ffff7af55e3 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#10 0x00007ffff7b238a2 in PyEval_EvalCode () from /usr/lib64/libpython2.7.so.1.0
#11 0x00007ffff7b30d81 in ?? () from /usr/lib64/libpython2.7.so.1.0
#12 0x00007ffff7b31146 in PyRun_FileExFlags () from /usr/lib64/libpython2.7.so.1.0
#13 0x00007ffff7b31a1d in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.7.so.1.0
#14 0x00007ffff7b3b26d in Py_Main () from /usr/lib64/libpython2.7.so.1.0
#15 0x00007ffff749d455 in __libc_start_main () from /lib64/libc.so.6
#16 0x0000000000400761 in _start ()
(gdb)

Revision history for this message
Andy Finch (fincha) wrote :

I don't quite understand where the crash is coming from, "QApplication was not created in the main() thread" is a QT generated message, OpenShot is a GTK app, so I'm a bit confused as to what is running here.

Revision history for this message
Don Harter (harterc2) wrote :

I am running kde/qt.
I upgraded to the latest qt4 tools package and that did not fix it.
I was beginning to suspect lib x11 or a fglrx64 proprietary driver issue.

I thought that many gnome programs run under kde through some interface. Perhaps there is a problem with that. Do you know what package that might be?

openshot is the only linux video editing program that has worked decently for me to edit x.264 video.

Revision history for this message
Andy Finch (fincha) wrote :

Sorry, I don't know. I always thought the GTK libraries were installed and run directly. Have you tried the export presets in the simple tab without changing anything in the advanced tab?

Revision history for this message
Don Harter (harterc2) wrote :

I have tried the preset tabs before and they also crashed.
I u pgraded my libx11 to the latest package and that did not fix it.

I moved the video files off my USB drive to a standard one. That did not fix it.

I tried to run gnome but that requires systemd in opensuse 12.2, and I have banned that program from my system.

I might temporarily install systemd so that I can try gnome.
I might also try without the proprietary video driver fglrx in X11. I wouldn't have hardware acceleration though. That driver has caused weird problems for some persons.

I did a little research and it seems that gnome and kde programs can coexist in suse12.2. The proper drivers just have to be loaded.

I don't think that I have enough disk space to install all the debug and source packages to use gdb further.

Revision history for this message
Don Harter (harterc2) wrote :

I tried it without the proprietary X driver,fglrx. That did not fix it. Rendering runs until it about 30% complete then it crashes as usual. I tried the simplified tabs again, selecting blue ray.

Revision history for this message
Don Harter (harterc2) wrote :

I started X with gnome. I then tried to export and it crashed.
The backtrace looks the same as the kde one. But what is that file doing there. I thought it was a kde file. Or is that a special way that suse does gnome, on top of qt/kde?
[New Thread 0x7fff7ffff700 (LWP 2921)]
[ac3_fixed @ 0x7fffa02c9100] Channel layout not specified
[ac3_fixed @ 0x7fffa02c9100] No channel layout specified. The encoder will guess the layout, but it might be incorrect.
[New Thread 0x7fff6c368700 (LWP 2922)]
WARNING: QApplication was not created in the main() thread.
sys:1: Warning: g_main_context_push_thread_default: assertion `acquired_context' failed

Program received signal SIGSEGV, Segmentation fault.
0x00007fffd3022a43 in x11EventSourceCheck (s=0x7fffb4839940) at kernel/qguieventdispatcher_glib.cpp:85
85 kernel/qguieventdispatcher_glib.cpp: No such file or directory.
(gdb) bt
#0 0x00007fffd3022a43 in x11EventSourceCheck (s=0x7fffb4839940) at kernel/qguieventdispatcher_glib.cpp:85
#1 0x00007ffff66b819b in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#2 0x00007ffff66b8622 in ?? () from /usr/lib64/libglib-2.0.so.0
#3 0x00007ffff66b8ae2 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#4 0x00007ffff45740d7 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0
#5 0x00007ffff4c1d508 in ?? () from /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/_gtk.so
#6 0x00007ffff7aef6aa in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#7 0x00007ffff7af235d in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#8 0x00007ffff7af235d in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0
#9 0x00007ffff7af55e3 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0
#10 0x00007ffff7b238a2 in PyEval_EvalCode () from /usr/lib64/libpython2.7.so.1.0
#11 0x00007ffff7b30d81 in ?? () from /usr/lib64/libpython2.7.so.1.0
#12 0x00007ffff7b31146 in PyRun_FileExFlags () from /usr/lib64/libpython2.7.so.1.0
#13 0x00007ffff7b31a1d in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.7.so.1.0
#14 0x00007ffff7b3b26d in Py_Main () from /usr/lib64/libpython2.7.so.1.0
#15 0x00007ffff749d455 in __libc_start_main () from /lib64/libc.so.6
#16 0x0000000000400761 in _start ()
(gdb)

I also tried it without the fglrx driver and that did not fix it.
The problem seems to be in qt toolkit or lilb X11. Both of those packages were upgraded, but bugs may still be in there. Perhaps I should regress to an earlier package.

Revision history for this message
Don Harter (harterc2) wrote :

I decided to try the memory leak tool valgrind. It reported what seemed to be many memory leaks. I wonder if some of those are false leaks.
Here is the command that I ran:
valgrind --tool=memcheck --trace-children=yes --error-limit=no --leak-check=full ./openshot | tee debug
Here is a summary of the final report:
==622== LEAK SUMMARY:
==622== definitely lost: 40,640 bytes in 82 blocks
==622== indirectly lost: 57,858 bytes in 1,797 blocks
==622== possibly lost: 619,101,321 bytes in 86,111 blocks
==622== still reachable: 476,260,399 bytes in 95,483 blocks
==622== suppressed: 0 bytes in 0 blocks
==622== Reachable blocks (those to which a pointer was found) are not shown.
==622== To see them, rerun with: --leak-check=full --show-reachable=yes
==622==
==622== For counts of detected and suppressed errors, rerun with: -v
==622== Use --track-origins=yes to see where uninitialised values come from
==622== ERROR SUMMARY: 186054124 errors from 5088 contexts (suppressed: 0 from 0)
My debug file is basically empty so I ,perhaps, should have run it with >&

Here are a few final lines. I will have to rerun it. It crashed before rendering was complete.
==622== 96,468,992 bytes in 23 blocks are possibly lost in loss record 20,865 of 20,867
==622== at 0x4C290FE: memalign (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==622== by 0x117214D6: mlt_pool_alloc (mlt_pool.c:125)
==622== by 0x15008FAA: allocate_buffer (producer_avformat.c:1219)
==622== by 0x1500C0DA: producer_get_image (producer_avformat.c:1528)
==622== by 0x117091DA: mlt_frame_get_image (mlt_frame.c:573)
==622== by 0x28F08A3C: deinterlace_yadif (filter_deinterlace.c:139)
==622== by 0x28F08F8E: filter_get_image (filter_deinterlace.c:235)
==622== by 0x117091DA: mlt_frame_get_image (mlt_frame.c:573)
==622== by 0x147D6FAD: get_image (filter_fieldorder.c:34)
==622== by 0x117091DA: mlt_frame_get_image (mlt_frame.c:573)
==622== by 0x147D5B7B: filter_get_image (filter_crop.c:77)
==622== by 0x117091DA: mlt_frame_get_image (mlt_frame.c:573)

Revision history for this message
Don Harter (harterc2) wrote :

Looking for memory leaks I tried libsafe and it still crashed.
I then rebuilt the mlt packages with electric fence. When I ran openshot the menu items were not functional.
I tried some other export formats but they also crashed. Perhaps it doesn't make a difference because of the format of my project files.

I used the DVD boot disk for openshot and was able to export on this computer what segfaults now.

Revision history for this message
Don Harter (harterc2) wrote :

This is a very old bug please close it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.