Ticket #7887 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Record activity segfaults soon after recording video

Reported by: martin.langhoff Owned by: dsd
Priority: blocker Milestone: 8.2.0 (was Update.2)
Component: distro Version: not specified
Keywords: joyride-2301:- joyride-2270:- blocks:8.2.0 Record-57:+ joyride-2363:+ 8.2-759:+ Cc: aly
Action Needed: test in release Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Following the smoketest, used Record to

  • capture a picture, view the pictrue
  • capture a vid, play the video,
  • capture audio, play audio

all in one session of Record. Shortly after recording and playing the video, Record dies - this is highly reproducible.

Attachments

org.laptop.RecordActivity-1.log (7.8 kB) - added by martin.langhoff 6 years ago.

Change History

Changed 6 years ago by kimquirk

  • keywords blocks:8.2.0 added
  • priority changed from normal to blocker

Changed 6 years ago by martin.langhoff

  • cc aly added
  • keywords joyride-2301 added
  • summary changed from Record activity locks us soon after recording video to Record activity segfaults soon after recording video

Confirmed against joyride-2301, attaching logs.

Reproduces consistently on 3 machines attempted (2 MPs, 1 B4). The log is almost identical in the 3, attaching one of them. To reproduce easily, follow the smoketest instructions but change the order of operations:

1st - capture an image 2nd - capture video and play it back 3rd - capture sound - crashes as soon as we press the "record" button

If run from Terminal the output is identical to the log attached, and it exits saying "Segmentation Fault". Not sure what rainbow isolation does to coredump files -

Apparently step 2 above leaves things in a bad state.

Changed 6 years ago by martin.langhoff

Changed 6 years ago by jg

  • owner changed from dsd to mstone
  • component changed from record-activity to distro

Changed 6 years ago by jg

  • owner changed from mstone to dsd

Changed 6 years ago by martin.langhoff

Attaching gdb to the process slowed it down to unusable, if I cannot use it, I cannot repro it under Record. Any other steps we could try taking...?

Changed 6 years ago by dsd

I wouldn't worry too much about it. To solve this and other bugs I'm next going to investigate building the old gstreamer and using the old record release. There are too many problems in this area to solve this time around :(

Changed 6 years ago by mstone

  • next_action changed from never set to diagnose

Changed 6 years ago by mstone

  • keywords joyride-2301:- joyride-2270:- added; joyride-2301 joyride-2270 removed

Changed 6 years ago by dsd

I can fix this quickly if we're OK with going back to an old gstreamer: http://lists.laptop.org/pipermail/devel/2008-August/018331.html

Changed 6 years ago by kimquirk

Should be available in next candidate (after 757) AND it needs a newer version of Record.

Changed 6 years ago by dsd

  • keywords Record-57:+ joyride-2263:+ added
  • status changed from new to closed
  • resolution set to fixed

fixed by reverting gstreamer and record code

Changed 6 years ago by dsd

  • status changed from closed to reopened
  • next_action changed from diagnose to add to build
  • resolution deleted

oops, can't close until we've got the packages in 8.2

Changed 6 years ago by dsd

  • keywords joyride-2363:+ added; joyride-2263:+ removed

Changed 6 years ago by martin.langhoff

FWIW - I can confirm it's still on 8.2-757 -

Changed 6 years ago by cscott

dsd, can you list exactly which packages & versions I should be pulling into 8.2, for the change log? If you could tag them for dist-olpc3-testing as well, that would help.

Changed 6 years ago by dsd

its all detailed in #7609

Changed 6 years ago by cscott

  • next_action changed from add to build to test in release

Added to the stable build stream; will be in 758.

Careful about closing this bug, though; we'll need to fix these problems "for real" in 9.1.

Changed 6 years ago by dsd

  • keywords 8.2-759:+ added
  • status changed from reopened to closed
  • resolution set to fixed

This is working in 759, created #8322 for the real fix

Note: See TracTickets for help on using tickets.