Recherche avancée

Sur d’autres sites (7835)

• It’s Piwik Analytics Survey time : Your Opinion Matters !

  8 janvier 2017, par Piwik Core Team — Community

  It’s been almost two years since our last survey. We were so happy to get the participation we did from the community last time and hope that you will once again share your thoughts !

  

  Fill in the survey

  Looking back on the previous survey, several features were implemented as a direct result :

  • New modern and beautiful app design in Piwik 3.0 !
  • Responsive Piwik User Interface
  • Custom Dimensions plugin
  • User ID for accurate cross device tracking
  • No more Referrer Spam in Piwik
  • Glossary of all terms used in Piwik
  • Huge performance improvements across the board
  • And much more…

  Now it is time to ask for your opinion again. Sure it’s only 15 short questions, but your time you take and energy you place in this endeavour will shape Piwik development and features for the near future. We really look forward to your ideas, your opinions and your suggestions. To get started click the box (or link) below :

  

  Fill in the survey !

  By the way, if you haven’t already make sure you sign up for our newsletter to make sure you get the latest Piwik news and information to your inbox ! You can subscribe here.

• memory leak in opencv/ffmpeg intregration ubuntu 16.04

  8 mai 2021, par Joshua

  Using ubuntu 16.04 opencv 2.4.9, ffmpeg 2.8.17. Below is the valgrind output. I am not using the ffmpeg library directly.

  


  The output buffer for encoding is initialized here, if we aren't encoding to a raw picture
https://github.com/opencv/opencv/blob/2.4.9/modules/highgui/src/cap_ffmpeg_impl.hpp#L1626

  


  Calling starts here, CvVideoWriter_FFMPEG::writeFrame
https://github.com/opencv/opencv/blob/2.4.9/modules/highgui/src/cap_ffmpeg_impl.hpp#L1264

  


  Which calls icv_av_write_frame_FFMPEG, passing the struct member outbuf
https://github.com/opencv/opencv/blob/2.4.9/modules/highgui/src/cap_ffmpeg_impl.hpp#L1365

  


  This call calls the FFMPEG api
https://github.com/opencv/opencv/blob/2.4.9/modules/highgui/src/cap_ffmpeg_impl.hpp#L1236

  


  According to the FFMPEG Docs for this version(n2.8.17), avcodec_encode_video2 only allocates memory if the input buffer is null, then the caller must free it. But if avcodec_encode_video is called, the output buffer parameter may be updated to point to the newly allocated data, and I assume it is supposed to be freed later with av_free. Anyways, since this isn't happening, everything here looks in order, but valgrind is still not happy.

  


  ==1038== 464,421,923 (477,288 direct, 463,944,635 indirect) bytes in 19,887 blocks are definitely lost in loss record 3,628 of 3,628
==1038==    at 0x4C33B3B: memalign (in /usr/local/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==1038==    by 0x4C33C22: posix_memalign (in /usr/local/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==1038==    by 0x185EF17F: av_malloc (in /usr/lib/x86_64-linux-gnu/libavutil-ffmpeg.so.54.31.100)
==1038==    by 0x185EF48D: av_mallocz (in /usr/lib/x86_64-linux-gnu/libavutil-ffmpeg.so.54.31.100)
==1038==    by 0x185DCB0E: av_buffer_create (in /usr/lib/x86_64-linux-gnu/libavutil-ffmpeg.so.54.31.100)
==1038==    by 0x185DD083: av_buffer_realloc (in /usr/lib/x86_64-linux-gnu/libavutil-ffmpeg.so.54.31.100)
==1038==    by 0x16EF46E8: av_dup_packet (in /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56.60.100)
==1038==    by 0x173716D2: avcodec_encode_video2 (in /usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56.60.100)
==1038==    by 0x8EA7377: ??? (in /usr/lib/x86_64-linux-gnu/libopencv_highgui.so.2.4.9)
==1038==    by 0x8EA8897: CvVideoWriter_FFMPEG::writeFrame(unsigned char const*, int, int, int, int, int) (in /usr/lib/x86_64-linux-gnu/libopencv_highgui.so.2.4.9)
==1038==    by 0x8EA89BD: cvWriteFrame_FFMPEG (in /usr/lib/x86_64-linux-gnu/libopencv_highgui.so.2.4.9)
==1038==    by 0x8EAA22E: CvVideoWriter_FFMPEG_proxy::writeFrame(_IplImage const*) (in /usr/lib/x86_64-linux-gnu/libopencv_highgui.so.2.4.9)


  


• It’s Piwik Analytics Survey time : Your Opinion Matters !

  10 juillet 2014, par Piwik Core Team — Community

  It’s been almost two years since our last survey. We were so happy to get the participation we did from the community last time and hope that you will once again share your thoughts !

  

  Fill in the survey

  Looking back on the previous survey, several features were implemented as a direct result :

  • New app design with Morpheus theme
  • Piwik Marketplace for Plugins
  • Visitor Profile
  • Performance and Reliability Improvements
  • Theming
  • Migrated from SVN to Github !
  • And much more…

  Now it is time to ask for your opinion again. Sure it’s only 20 short questions, but your time you take and energy you place in this endeavour will shape Piwik development and features for the near future. We really look forward to your ideas, your opinions and your suggestions. To get started click the box (or link) below :

  

  Fill in the survey !

  By the way, if you haven’t already make sure you sign up for our newsletter to make sure you get the latest Piwik news and information to your inbox ! You can subscribe here.