title: Why the stride of image returned from Tango Support C-API is strange?
body: <p>Anyone find similar issue: Strange image.stride returned by TangoSupport_getLatestImageBufferAndNewDataFlag in Tango Support C-API (Qianru July, 2016) ?</p>
  
  <pre><code>.....
  
  TangoImageBuffer* b = nullptr;
  
  TangoSupport_getLatestImageBufferAndNewDataFlag(image_buffer_manager, &amp;b,   &amp;new_image);
  
  if(new_image)
  {
      LOGE("b: %p: width %zu, stride %zu", b, b-&gt;width, b-&gt;stride );
  }
  ....
  </code></pre>
  
  <p>The output is:</p>
  
  <pre><code>b: 0x4cdd3ca8: width 1280, stride 7471215
  b: 0x4cdd3c78: width 1280, stride 0
  b: 0x4cbbe500: width 1280, stride 6881398
  b: 0x4cdd3ca8: width 1280, stride 7471215
  .... repeat from the above line ...
  </code></pre>
  
  <p>Pointer, and width look fine. But the stride looks strange.</p>