Recherche avancée

Sur d’autres sites (6746)

• Catch "Unfortunately 'app' has stopped working" Error

  2 juillet 2015, par cadesalaberry

  I am using a very unstable library on Android that crashes sporadically. I start it using the startActivity() in my code.

  The unstable part of the code is doing a lot of video processing and uploading the result to a server. I do not really mind if the activity crashes, but I need to signal the server that it did.

  The crash comes from a memory leak (no time to solve it yet). Is there a way I can catch the error a display a more friendly/funny message instead ?

  try {
  
      context.startActivity(intent);
  
  } catch (ApplicationCrashedException e) {
  
      server.notifyServerOfCrash();
  
      toast("I really disliked your face...");
  
  }

  Edit : Here is the Error :

  java.lang.OutOfMemoryError
  
    at dalvik.system.VMRuntime.newNonMovableArray(Native Method)
  
    at java.nio.MemoryBlock.allocate(MemoryBlock.java:125)
  
    at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:72)
  
    at io.cine.android.streaming.FFmpegMuxer.writeSampleData(FFmpegMuxer.java:151)
  
    at io.cine.android.streaming.AndroidEncoder.drainEncoder(AndroidEncoder.java:128)
  
    at io.cine.android.streaming.TextureMovieEncoder.handleFrameAvailable(TextureMovieEncoder.java:264)
  
    at io.cine.android.streaming.TextureMovieEncoder$EncoderHandler.handleMessage(TextureMovieEncoder.java:409)
  
    at android.os.Handler.dispatchMessage(Handler.java:102)
  
    at android.os.Looper.loop(Looper.java:136)
  
    at io.cine.android.streaming.TextureMovieEncoder.run(TextureMovieEncoder.java:219)
  
    at java.lang.Thread.run(Thread.java:841)

  For some reason once the BroadcastActivity runs out of memory, the Activity gets killed and comes back to the previous one. It then displays the ’app’ has stopped working Dialog. If I press OK, it kills the entire application and comes back to the home screen.

  Ideally I would just have it come back to the previous activity notifying the server silently. (Not killing the application)

• FFMPEG gives "Error opening Filters" error

  18 juin 2015, par liberation

  I am trying to compress a file and store it in MongoDB via GridFS. I am compressing it using a node module called stream-transponder which uses ffmpeg to compress it. My code looks like this

  bodyParser.process('video/*', function(stream, req, next) {
  
      var busboy = new Busboy({ headers : req.headers });
  
      var fileId = new mongo.ObjectId();
  
      var writestream = gfs.createWriteStream({
  
              filename: (fileId.toString()) + ".mp4",
  
              _id : fileId,
  
              mode : "w",
  
              content_type  : "video/mp4"
  
      });
  
      new Transcoder(stream)
  
          .videoCodec('h264')
  
          .videoBitrate(800 * 1000)
  
          .fps(25)
  
          .aspectRatio(1.7777777)
  
          .audioCodec('aac')
  
          .sampleRate(44100)
  
          .channels(2)
  
          .audioBitrate(128 * 1000)
  
          .format('mp4')
  
      .on('finish', function () {
  
          req.custom = fileId;
  
          console.log(fileId);
  
          next();
  
      }).stream().pipe(writestream);
  
  
  
  });

  The ffmpeg command line call that stream-transcoder makes looks like this :

  ffmpeg -i - -vcodec h264 -b:v 800000 -r 25 -aspect 1.7777777 -acodec aac -ar 44100 -ac 2 -ab 128000 -f avi pipe:1

  sometime’s the command looks like this

  ffmpeg -i - -vf scale=min(trunc(320/hsub)*hsub\,trunc(a*240/hsub)*hsub):min(trunc(240/vsub)*vsub\,trunc(320/a/vsub)*vsub) -vcodec h264 -b:v 800000 -r 25 -acodec libfaac -ar 44100 -ac 2 -ab 128000 -f mp4 -movflags frag_keyframe+faststart pipe:1

  eventhough I am uploading the same exact file I uploaded when I got the former command. They both give the same error (Opening Filters error).

  I tried running encoding a file straight from the terminal with this command :

  ffmpeg -i VIDEO0077.mp4 -c:v h264 -preset slow -crf 22 -c:a copy output2.mp4

  and it worked like a charm. I am not sure what’s causing the Error Opening Filters error.

• nginx +unicorn+rails+"upstream prematurely closed connection while reading response header from upstream" 502 bad gateway error

  13 juin 2015, par Rajesh Raikwar

  I’ve been scratching my head over this 502 gateway error while converting a video(approx 10mb) using ffmpeg. files of less than 2mb works fine
  when I try to upload + convert using webrick ,it works fine.
  I have client_max_body_size 1G set.

  for testing purpose I have added these in nginx conf file

  proxy_connect_timeout 600s;
  
      proxy_send_timeout    600s;
  
      proxy_read_timeout    600s;
  
      send_timeout          600s;
  
  
  
      proxy_buffer_size           32k;
  
      proxy_buffers               4 32k;
  
      proxy_busy_buffers_size     32k;
  
      proxy_temp_file_write_size  32k;
  
  
  
      fastcgi_buffers 8 16k;
  
      fastcgi_buffer_size 32k;     
  
  
  
  timeout for unicorn is set as 
  
  timeout 300 , in unicorn.rb

  Please help.