question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Invalid data found when processing input

See original GitHub issue

Hi,

I get the following output/error after some tests ran successfully:

> sitespeed_measurements@1.0.0 all_mobile_chrome_lte_video /**hidden**/sitespeed.io
> npm run all_mobile_chrome_lte_video_firstView && npm run all_mobile_chrome_lte_video_repeatedView


> sitespeed_measurements@1.0.0 all_mobile_chrome_lte_video_firstView /**hidden**/sitespeed.io
> npm run async_mobile_chrome_lte_video_firstView && npm run defer_mobile_chrome_lte_video_firstView && npm run original_mobile_chrome_lte_video_firstView && npm run preload_mobile_chrome_lte_video_firstView


> sitespeed_measurements@1.0.0 async_mobile_chrome_lte_video_firstView /**hidden**/sitespeed.io
> sitespeed.io --config mobile_chrome_lte_video_firstView.json urls_async.txt

[2017-10-12 09:53:19] INFO: Versions OS: darwin 16.7.0 nodejs: v6.11.1 sitespeed.io: 5.6.4 browsertime: 1.9.4 coach: 0.36.0
[2017-10-12 09:53:20] INFO: Starting chrome for analysing https://**hidden**.cloudfront.net/async_test/sf/index.html 5 time(s)
[2017-10-12 09:53:20] INFO: Testing url https://**hidden**.cloudfront.net/async_test/sf/index.html run 1
[2017-10-12 09:53:27] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 09:53:45] INFO: Converting video to 60 fps
[2017-10-12 09:55:01] INFO: Testing url https://**hidden**.cloudfront.net/async_test/sf/index.html run 2
[2017-10-12 09:55:08] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 09:55:28] INFO: Converting video to 60 fps
[2017-10-12 09:56:47] INFO: Testing url https://**hidden**.cloudfront.net/async_test/sf/index.html run 3
[2017-10-12 09:56:53] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 09:57:10] INFO: Converting video to 60 fps
[2017-10-12 09:58:06] INFO: Testing url https://**hidden**.cloudfront.net/async_test/sf/index.html run 4
[2017-10-12 09:58:12] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 09:58:28] INFO: Converting video to 60 fps
[2017-10-12 09:59:30] INFO: Testing url https://**hidden**.cloudfront.net/async_test/sf/index.html run 5
[2017-10-12 09:59:36] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 09:59:51] INFO: Converting video to 60 fps
[2017-10-12 10:00:46] INFO: 86 requests, 945.37 kb, backEndTime: 1.09s (±160.96ms), firstPaint: 2.48s (±269.93ms), firstVisualChange: 2.99s (±279.82ms), DOMContentLoaded: 3.02s (±274.48ms), Load: 5.66s (±830.07ms), speedIndex: 4650 (±276.36), visualComplete85: 7.62s (±302.22ms), lastVisualChange: 9.16s (±1.08s), rumSpeedIndex: 3252 (±418.47) (5 runs)
[2017-10-12 10:00:48] INFO: Starting chrome for analysing https://**hidden**.cloudfront.net/async_test/mes/index.html 5 time(s)
[2017-10-12 10:00:48] INFO: Testing url https://**hidden**.cloudfront.net/async_test/mes/index.html run 1
[2017-10-12 10:00:54] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 10:01:12] INFO: Converting video to 60 fps
[2017-10-12 10:02:07] INFO: Testing url https://**hidden**.cloudfront.net/async_test/mes/index.html run 2
[2017-10-12 10:02:12] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 10:02:27] INFO: Converting video to 60 fps
[2017-10-12 10:03:10] INFO: Testing url https://**hidden**.cloudfront.net/async_test/mes/index.html run 3
[2017-10-12 10:03:15] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 10:03:30] INFO: Converting video to 60 fps
[2017-10-12 10:04:11] INFO: Testing url https://**hidden**.cloudfront.net/async_test/mes/index.html run 4
[2017-10-12 10:04:17] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 10:04:32] INFO: Converting video to 60 fps
[2017-10-12 10:05:16] INFO: Testing url https://**hidden**.cloudfront.net/async_test/mes/index.html run 5
[2017-10-12 10:05:22] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 10:05:36] INFO: Converting video to 60 fps
[2017-10-12 10:06:20] INFO: 84 requests, 848.94 kb, backEndTime: 769ms (±37.55ms), firstPaint: 1.94s (±58.67ms), firstVisualChange: 2.18s (±51.68ms), DOMContentLoaded: 2.14s (±55.49ms), Load: 4.25s (±569.04ms), speedIndex: 3218 (±65.22), visualComplete85: 2.80s (±63.98ms), lastVisualChange: 6.99s (±124.45ms), rumSpeedIndex: 2590 (±655.82) (5 runs)
[2017-10-12 10:06:22] INFO: Starting chrome for analysing https://**hidden**.cloudfront.net/async_test/pl/index.html 5 time(s)
[2017-10-12 10:06:22] INFO: Testing url https://**hidden**.cloudfront.net/async_test/pl/index.html run 1
[2017-10-12 10:06:28] INFO: Start screenrecord on device 04157df4ea453f2f
[2017-10-12 10:06:42] INFO: Converting video to 60 fps
(node:51133) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Command failed: ffmpeg -i /**hidden**/sitespeed.io/results_mobile_chrome_lte_video_firstView/pages/**hidden**.cloudfront.net/async_test/pl/index.html/data/video/0.mp4 -r 60 /**hidden**/sitespeed.io/results_mobile_chrome_lte_video_firstView/pages/**hidden**.cloudfront.net/async_test/pl/index.html/data/video/tmp.mp4
ffmpeg version 3.3.4 Copyright (c) 2000-2017 the FFmpeg developers
  built with Apple LLVM version 8.1.0 (clang-802.0.42)
  configuration: --prefix=/usr/local/Cellar/ffmpeg/3.3.4 --enable-shared --enable-pthreads --enable-gpl --enable-version3 --enable-hardcoded-tables --enable-avresample --cc=clang --host-cflags= --host-ldflags= --enable-libfreetype --enable-libmp3lame --enable-libx264 --enable-libxvid --enable-opencl --enable-videotoolbox --disable-lzma --enable-vda
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale      4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc    54.  5.100 / 54.  5.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fb895802c00] moov atom not found
/**hidden**/sitespeed.io/results_mobile_chrome_lte_video_firstView/pages/**hidden**.cloudfront.net/async_test/pl/index.html/data/video/0.mp4: Invalid data found when processing input

mobile_chrome_lte_video_firstView.json

{
  "browsertime": {
    "chrome": {
      "args": "",
      "android": {
        "package": "com.android.chrome"
      }
    },
    "connectivity": {
      "engine": "external",
      "profile": "3gfast"
    },
    "iterations": 5,
    "video": true,
    "speedIndex": true
  },
  "graphite": {
    "host": "localhost",
    "port": "2003",
    "httpPort": **hidden**,
    "webHost": **hidden**,
    "namespace": **hidden**,
    "arrayTags": true
  },
  "plugins": {
    "load": "analysisstorer"
  },
  "utc": true,
  "resultBaseURL": "http://localhost:8080",
  "outputFolder": "results_mobile_chrome_lte_video_firstView"
}

urls_async.txt

https://**hidden**.cloudfront.net/async_test/sf/index.html **hidden**
https://**hidden**.cloudfront.net/async_test/mes/index.html **hidden**
https://**hidden**.cloudfront.net/async_test/pl/index.html **hidden**
https://**hidden**.cloudfront.net/async_test/ads/index.html **hidden**

Does anybody had this problem before? Is this the correct relation: https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/638 ?

Thank you and best regards Philipp

PS:

The error occures only sometimes, rerunning the test at this step is a workaround. It could be also better if the tests continue instead of failing hard.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:12 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
soulgalorecommented, Nov 3, 2017

@moehlone next week I’ll work on the project. I’ll add a task for tightening video handling for mobile,

0reactions
soulgalorecommented, Jun 15, 2018

I’ve changed this in BT 3.0 and sitespeed.io 7.0, please re-open if this is still an issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

ffmpeg now says "Invalid data found when processing input"
I tried generating a ppm without it and the Invalid data found when processing input error doesn't occur. I see that the last...
Read more >
"Invalid data found when processing input" happening for ...
Trying to re-contain them into MKV's but I keep getting "moov atom not found. <file name>: Invalid data found when processing input".
Read more >
Invalid data found when processing input | ffmpeg
I'm trying to concat multiple videos with ffmpeg, im using a text file as input but im getting " ...
Read more >
Ffmpeg | Invalid data found when processing input
Hello. I'm unable to concatenate 'webm' files due to some "Invalid data found when processing input". Script to concat the files
Read more >
ffmpeg concat always return error `Invalid data found when ...
-f concat is the switch that is supposed to specify the "demuxer", so it needs to be placed before -i Concat.txt .
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found