Recherche avancée

Médias (91)

Autres articles (95)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (7456)

  • Low memory killer because of ffmpeg in Android

    22 avril 2021, par engineer ece

    I'm running an application in Android embedded card. The application is implemented in C. It runs an ffmpeg process using system() API which streams transport stream data over IP. When I started the application, approximately 2 hours later, low memory killer daemon is killing the background processes slowly. After some time it's killing the application also. And the GUI screen is hanged completely.
    
ffmpeg command :
    
ffmpeg -loglevel quiet -re -i "udp://192.168.47.1:8080?buffer_size=10000000&fifo_size=100000000&overrun_nonfatal=1" -map 0:p:1 -f mpegts udp://192.168.47.172:9090?pkt_size=1316

    


    low memory killer log :

    


    [ 7975.838158@2] lowmemorykiller: Killing 'droid.deskclock' (4779), adj 906,
[ 7975.838158@2]    to free 18940kB on behalf of 'kswapd0' (1978) because
[ 7975.838158@2]    cache 109744kB is below limit 114688kB for oom_score_adj 529
[ 7975.838158@2]    Free memory is 9276kB above reserved. nonmove free (32936kB),(63700kB)
[ 7976.045769@2] lowmemorykiller: Killing 'd.process.media' (4902), adj 906,
[ 7976.045769@2]    to free 23028kB on behalf of 'kswapd0' (1978) because
[ 7976.045769@2]    cache 112320kB is below limit 114688kB for oom_score_adj 529
[ 7976.045769@2]    Free memory is 5440kB above reserved. nonmove free (31148kB),(66164kB)


    


    Query :

    


      

    • Does ffmpeg consume more CPU & memory over the course of time, which in turn causing low memory killer ?

      • 


    


  • avcodec/wmaprodec : Make decoders init-threadsafe

    5 mai 2021, par Andreas Rheinhardt
    avcodec/wmaprodec : Make decoders init-threadsafe

    In this case this actually fixes a potential data race : The static VLC
    
tables were reinitialized every time an AVCodecContext has been
    
initialized ; while the mutex in avcodec_open2() ensured that the VLCs
    
could not be initialized concurrently by multiple threads, nothing
    
guaranteed that these VLCs are not read concurrently (when decoding a
    
packet with an already initialized AVCodecContext) while another thread
    
initializes them. This is undefined behaviour despite the values being
    
written coinciding with the earlier values.
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
    • [DH] libavcodec/wmaprodec.c

  • avcodec/jpeg2000dec : Make decoder init-threadsafe

    7 mai 2021, par Andreas Rheinhardt
    avcodec/jpeg2000dec : Make decoder init-threadsafe

    The JPEG-2000 decoder and encoder share common luts ; the decoder
    
initializes them once, guarded by a dedicated AVOnce, whereas
    
the encoder initializes them always during init. This means that
    
the decoder is not init-threadsafe ; in fact there is a potential
    
data race because these luts can be initialized while an active
    
decoder/encoder is using them.
    

    Fix this and make the decoder init-threadsafe by making the
    
initialization function guard initialization itself with a dedicated
    
AVOnce.
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
    • [DH] libavcodec/jpeg2000.c
    • [DH] libavcodec/jpeg2000dec.c

Navigation