After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 742943 - Pitivi crashes early with "Internal data stream error"
Pitivi crashes early with "Internal data stream error"
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: General
0.94
Other Linux
: Normal normal
: 0.95
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on: 743326
Blocks:
 
 
Reported: 2015-01-14 23:00 UTC by owlbrudder
Modified: 2015-01-22 00:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Terminal output captured after Pitivi freezes (3.15 KB, text/plain)
2015-01-14 23:00 UTC, owlbrudder
Details
Terminal output two (21.39 KB, text/plain)
2015-01-15 00:45 UTC, owlbrudder
Details
Terminal output three (2.39 KB, text/plain)
2015-01-15 01:25 UTC, owlbrudder
Details
gdb trace one (65.07 KB, text/plain)
2015-01-15 02:45 UTC, owlbrudder
Details

Description owlbrudder 2015-01-14 23:00:57 UTC
Created attachment 294558 [details]
Terminal output captured after Pitivi freezes

I have just discovered Pitivi and it looks as though it will be great for what I want. I am running Fedora 21 on a Lenovo Z61t laptop.

The trouble is, Pitivi freezes after a minute or two. For example, I can start the application, load two small .avi clips and put them onto the timeline, but as soon as I 'slide' the second so it abuts the first on the time line, the GUI freezes. I don't know whether this action is the cause, but I don't get a chance to explore other features of the application before it freezes.

Interestingly, when I open a terminal and try to 'kill' the process, 'ps -ael' reports no instances of pitivi running. The GUI remains on my Activities screen and I can find no way of killing it, other than logging out.

I ran Pitivi from a terminal and had the same problem, but captured the output to the terminal and note it reports an 'Internal data stream error' - see attached. The terminal was also frozen at this time. When I opened another terminal and 'kill'ed the first terminal, both Pitivi and the terminal closed correctly.

Before I go to the trouble of installing all the debug packages and capturing the gdb output, is there something simple I am doing wrong? Is there something I have not installed?
Comment 1 owlbrudder 2015-01-15 00:44:31 UTC
I have solved one of my issues: I was using ps with the wrong options, to find the pitivi process - I should have been using 'ps -aux pitivi' which works.

I installed the debug rpms, ran pitivi from a terminal and used gdb from another terminal to monitor it. With gdb running, I could not crash pitivi - maybe I didn't work it hard enough?

For what it is worth, I ran it again from a command prompt and captured the resulting trace from the terminal - see attached 'Terminal output two'.
Comment 2 owlbrudder 2015-01-15 00:45:16 UTC
Created attachment 294563 [details]
Terminal output two
Comment 3 Mathieu Duponchelle 2015-01-15 00:53:55 UTC
Hey, can you try with our daily bundles whether you can reproduce the issue ?

http://fundraiser.pitivi.org/download-bundles
Comment 4 owlbrudder 2015-01-15 01:24:35 UTC
Hi Mathieu.

I downloaded 'Latest daily build Pitivi 32 bits bundle: pitivi-latest-x86.tar', extracted it to a new directory and ran it. I was able to select my simple project, that has no clips included. The main window came up as expected. I attempted to add videos by selecting the same two clips I have been working with. As soon as I clicked 'Add', the program crashed. I will attach the latest terminal output as 'Terminal output three'.
Comment 5 owlbrudder 2015-01-15 01:25:20 UTC
Created attachment 294564 [details]
Terminal output three
Comment 6 owlbrudder 2015-01-15 02:44:32 UTC
For what it is worth, I have attached the gdb trace from the pitivi-0.94-x86 session that crashed. This attachment is labelled 'gdb trace one'.
Comment 7 owlbrudder 2015-01-15 02:45:12 UTC
Created attachment 294567 [details]
gdb trace one
Comment 8 owlbrudder 2015-01-15 06:54:32 UTC
I have found Pitivi (the Fedora version, not the daily build) seems to work well without freezing, as long as I use only video clips of the same type. For example, I can reliably get it to freeze by selecting two different types (say, an mp4 and a flv) and trying to manipulate them together. Sometimes it freezes while I am manipulating the two clips on the timeline and sometimes it freezes when I exit the application. Always when I have two dissimilar clips on the timeline, it seems I am unable to play the video of either clip.

pitivi-0.94-x86 crashes if I select two dissimilar clips and try to import them into the project. I tried selecting a single mp4 and it imported OK, but I could not append it to the timeline. I deleted that clip and tried another mp4 (a larger one) and pitivi-0.94-x86 crashed with a segmentation fault.
Comment 9 Thibault Saunier 2015-01-15 08:24:27 UTC
A lot of development happend in the backend recently so it would be a good idea for you to test the latest faily build bundle, did you test that?
Comment 10 owlbrudder 2015-01-15 23:34:44 UTC
Yes, I took the latest daily bundle yesterday - that is the one I refer to as pitivi-0.94-x86. I have been unable to get as far as placing a clip onto the timeline with that bundle, so there must be something not right about my setup, I think.

The Pitivi version from the Fedora repository seems to work reasonably well, as long as I only add similar video clips to the project (all the same type, same resolution etc). I have been unable to get the Fedora version to play a .flv clip - the video window just stays blank if I try to use a .flv.
Comment 11 Thibault Saunier 2015-01-16 09:30:07 UTC
(In reply to comment #10)
> Yes, I took the latest daily bundle yesterday - that is the one I refer to as
> pitivi-0.94-x86. I have been unable to get as far as placing a clip onto the
> timeline with that bundle, so there must be something not right about my setup,
> I think.

With the bundles there is no such thing as setup, it would be nice of you to share clip that fail so that we can investigate.

Have a look at http://wiki.pitivi.org/wiki/Bug_reporting#Providing_debugging_information if you need some place to share them.
Comment 12 owlbrudder 2015-01-18 07:16:31 UTC
Hi, Thibault. I need a password to post my video clip files to your repository. I see from the documentation that I need to get this using something called 'IRC' - can you explain how I am to do this? (I have been programming since 1980 and never used IRC - go figure!)
Comment 13 owlbrudder 2015-01-19 02:56:34 UTC
Rather than worry about FTP etc, the clips I am trying to use are on YouTube. I downloaded them using Firefox with the DownloadHelper extension.

The first is the .flv version of https://www.youtube.com/watch?v=NRrVyz9cVtU '9 most useful Sailing/Boating Knots (Revised - better angle)'. The version of Pitivi from the Fedora repository (Version 0.94) allows me to place this clip on the timeline, but does not render it in the video window and Pitivi locks up fairly soon after I try clicking on the timeline, to locate the cursor at various times within the clip.

The second is the .mp4 version of https://www.youtube.com/watch?v=GcJ9QSuUT3c ' 60 miles "Round the Island" in a Mirror Dinghy'. The version of Pitivi from the Fedora repository (Version 0.94) allows me to place this clip on the timeline, but does not render it in the video window if I also have the above .flv clip on the timeline. If I create a project containing only this clip, it all seems to work OK. I further note that this version seems to work OK as long as all the clips on the timeline are exactly the same type, with the same resolution and same size.

The version of Pitivi from the daily build I downloaded (Version pitivi-0.94-x86) does not allow me to add any clips to the project at all - it just crashes.
Comment 14 Thibault Saunier 2015-01-19 07:43:07 UTC
I just pushed the fix:

commit c34f73983a88e802be28bcbd6623e89667dcb3f4
Author: Thibault Saunier <tsaunier@gnome.org>
Date:   Mon Jan 19 08:25:28 2015 +0100

    utils:pipeline: Fix backtrace

    TypeError: argument of type 'NoneType' is not iterable

The bundle is building https://jenkins.arracacha.collabora.co.uk/job/pitivi-bundling/306/console and should be ready in an hour or so.
Comment 15 owlbrudder 2015-01-19 23:51:51 UTC
Thanks Thibault. I have downloaded the latest daily build and it is much better, but still not right.

First, I tried running it as soon as downloaded, but it crashed as soon as I tried importing clips into the (new) project. I suspect something in memory had not been cleared from the previous version's crash, so I logged out and in again.

With a fresh login, I was able to run for quite a long time. I first added the .flv clip to the timeline and this worked, but the preview window did not display the current location's image. I tried moving the cursor along the timeline, but it would not move.

I removed that clip from the timeline, then added the .mp4 clip, followed by the .flv clip, on the timeline. Now I could move the cursor along the .mp4 clip and images displayed correctly in the video window, but as soon as I tried to move the cursor over the .flv clip, it became immovable. It would no longer move back to the .mp4.

I deleted both clips from the timeline, then added them back in the same order. Again, I was able to move the cursor over the .mp4 and the video preview worked, but both these behaviours stopped as soon as I tried to move the cursor over the .flv.

I tried rendering the current clips as a movie, to see what would happen. I was able to select the location, then tried to edit project settings. As soon as I clicked on the button to change the aspect ratio, Pitivi crashed.

I tried restarting Pitivi, but was back to the old problem of it crashing as soon as I tried to import the two clips to the project.

To see if there was a memory issue, I logged out and in again, but Pitivi again crashed as soon as I attempted to import the two clips to the project.

Without logging out and in, I tried Pitivi again and this time imported only the .flv clip to the project and this was successful. As soon as I then tried to import the .mp4 clip, Pitivi crashed.

I tried again, this time importing only the .flv clip and placing it on the timeline. This much worked, but it would still not let me move the time cursor and displayed nothing in the preview window.

I removed the .flv clip from the project and imported the .mp4, which I placed on the timeline. This time, the cursor would not move and the video window was blank.

I closed Pitivi and restarted it. It closed as soon as I clicked 'Add' to import the .mp4 clip by itself.

I tried again and this time selected the .mp4, but paused for a few seconds to consider what to do next. Before I even clicked the 'Add' button, Pitivi crashed.

Do you have debuginfo packages I can install, to enable me to run gdb over the daily build executable? I have already installed the debuginfo packages for the version in the Fedora repository.

Please let me know if there are any other tests you would like me to try.
Comment 16 Mathieu Duponchelle 2015-01-21 17:36:15 UTC
Hey, flv support for our use case is currently broken on master branches, working on that.
Comment 17 owlbrudder 2015-01-21 21:49:02 UTC
Thanks, Mathieu - I am glad to know the problem is not at my end. I will look forward to the next version with working flv support.  "8-)
Comment 18 Mathieu Duponchelle 2015-01-22 00:09:47 UTC
I proposed a patch to fix flv support ( https://bugzilla.gnome.org/show_bug.cgi?id=743326 ), marking this bug as dependent. Once this is merged, you'll be able to crash later :P
Comment 19 owlbrudder 2015-01-22 00:31:37 UTC
Thanks for the prompt attention, Mathieu. As this bug is dependent upon 743326, will I automatically be notified as it progresses, or will I have to follow 743326 by opening that page and refreshing it in my browser?
Comment 20 Mathieu Duponchelle 2015-01-22 00:35:42 UTC
Unfortunately othe bugs exist in flvdemux as I can see now, I would advise using another format for now, sorry about that !
Comment 21 Mathieu Duponchelle 2015-01-22 00:36:21 UTC
I think you'll be notified, but you can add yourself to the CC list on the other bug to make sure
Comment 22 owlbrudder 2015-01-22 00:58:31 UTC
(In reply to comment #20)
> Unfortunately othe bugs exist in flvdemux as I can see now, I would advise
> using another format for now, sorry about that !

OK - I will add myself to the CC list on 743326 and avoid using flv in the mean time.

I will give the software another try, avoiding flv, to see if the rest of it works OK for me.

I notice this bug status is shown as 'RESOLVED' 'FIXED' - is that accurate? I would have thought it would still be unresolved.

Thanks for all your help.
Comment 23 Mathieu Duponchelle 2015-01-22 00:59:52 UTC
Best would be to open a new bug, this one becomes a bit long and unrelated to the first issue