#10183 NORM Not Tri: Record-82 crashes on os204 while saving a just-recorded audio clip

[Zarro Boogs per Child]

#10183: Record-82 crashes on os204 while saving a just-recorded audio clip
---------------------------------------+------------------------------------
           Reporter:  mikus            |       Owner:  dsd                              
               Type:  defect           |      Status:  new                              
           Priority:  normal           |   Milestone:  Not Triaged                      
          Component:  record-activity  |     Version:  Development build as of this date
         Resolution:                   |    Keywords:                                   
        Next_action:  diagnose         |    Verified:  0                                
Deployment_affected:                   |   Blockedby:                                   
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by mikus):

 Replying to [comment:8 Quozl]:
 > {{{
 > sugar-launch org.laptop.RecordActivity
 > }}}
 What that does is put output to Terminal (which acts as a console), rather
 than to .sugar/default/logs

 > {{{
 > strace -o /tmp/record.strace -f \
 >   sugar-launch org.laptop.RecordActivity
 > }}}
 Had to make several attempts.  On the XO-1.5 (os204), with python-psyco
 present, "plain" launching of Record-82 consistently resulted in the
 #10183 problem (Terminal showed segment fault).  But with 'strace', I was
 NOT able to reproduce the #10183 problem on the XO-1.5.

 So I tried on the XO-1 (os284py), with python-psyco present.  With
 'strace', things happened in MINUTES rather than in seconds (as on the
 XO-1.5).  [In fact, the button in Audio never turned red (to indicate
 audio recording was in progress).]  But when I got tired of waiting, and
 clicked again (i.e., the "stop" click) on the button, Record-82 vanished
 just as it did on os204.

 Am attaching the tail end of the console output, plus the whole 'strace'
 recording.  Just in case, also took a dump of os284py (after Record had
 ended) -- but this was *not* of a "clean" system -- I had been trying
 Record multiple times without re-booting inbetween.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10183#comment:9>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system