
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (50)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
HTML5 audio and video support
13 avril 2011, parMediaSPIP 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 (...)
Sur d’autres sites (9908)
-
Merge commit ’64034849dad8410bedbe1def4c533490fb85cc4a’
2 janvier 2016, par Hendrik Leppkes -
Fatal error detected by JRE : libavcodec involved
16 novembre 2015, par hdfI’m experiencing this issue whenever I’m trying to run my java program. Could someone give me a clues on how to fix it ?
EDIT : the issue only occurs after a new environment has been set up.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#
#
# JRE version: OpenJDK Runtime Environment (7.0_85-b01) (build 1.7.0_85-b01)
# Java VM: OpenJDK 64-Bit Server VM (24.85-b03 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 2.6.1
# Distribution: Ubuntu 14.04 LTS, package 7u85-2.6.1-5ubuntu0.14.04.1
# Problematic frame:
# C [libavcodec.so.52.123.0+0x442060]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
--------------- T H R E A D ---------------
Current thread (0x00007f8f70141800): JavaThread "threadpool-14" daemon [_thread_in_native, id=14508, stack(0x00007f8fa73a0000,0x00007f8fa74a1000)]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=128 (), si_addr=0x0000000000000000
Registers:
RAX=0x00007f8f701d2110, RBX=0x00007f8fa65030d0, RCX=0x00007f8fa688efd0, RDX=0x00007f8fa68904b0
RSP=0x00007f8fa749f380, RBP=0x00007f8fa749f3d8, RSI=0x000000000000000c, RDI=0x00007f8f701d2110
R8 =0x0000000000000000, R9 =0x0000000000000000, R10=0x00007f8fc5eb56e0, R11=0x00007f8fc591af50
R12=0x0000000000000000, R13=0x00007f8f701419d8, R14=0x00007f8fa749f578, R15=0x00007f8f70141800
RIP=0x00007f8fa688f060, EFLAGS=0x0000000000010202, CSGSFS=0x0000000000000033, ERR=0x0000000000000000
TRAPNO=0x000000000000000d
Top of Stack: (sp=0x00007f8fa749f380)
0x00007f8fa749f380: 00007f8fa688f1a5 00007f8fa688ffe5
0x00007f8fa749f390: 00007f8fa6890025 00007f8fa6890065
0x00007f8fa749f3a0: 00007f8fa68900a5 00007f8fa68900e5
0x00007f8fa749f3b0: 00007f8fa6890125 00007f8fa68904b5
0x00007f8fa749f3c0: 00007f8fa6890678 00007f8fa7198f31
0x00007f8fa749f3d0: 0000000000000000 00007f8f70158540
0x00007f8fa749f3e0: 00007f8fa749f468 00007f8fa71966ae
0x00007f8fa749f3f0: 0000000776cfa560 0000000776cfa560...
Instructions: (pc=0x00007f8fa688f060)
0x00007f8fa688f040: c4 e3 5d 0c c0 55 c5 e4 5c c8 c5 e4 58 c0 c5 fc
0x00007f8fa688f050: 29 07 c5 fc 29 4f 20 c3 0f 1f 84 00 00 00 00 00
0x00007f8fa688f060: c5 fc 28 57 40 c5 fc 28 5f 60 c5 ec 5c fb c5 ec
0x00007f8fa688f070: 58 d3 c5 c4 57 3d 26 e0 13 00 c5 ec c6 df be c5
Register to memory mapping:
RAX=0x00007f8f701d2110 is an unknown value
RBX=0x00007f8fa65030d0: av_fft_calc+0 in /usr/local/lib/libavcodec.so.52.123.0 at 0x00007f8fa644d000
RCX=0x00007f8fa688efd0: <offset 0x441fd0="0x441fd0"> in /usr/local/lib/libavcodec.so.52.123.0 at 0x00007f8fa644d000
RDX=0x00007f8fa68904b0: <offset 0x4434b0="0x4434b0"> in /usr/local/lib/libavcodec.so.52.123.0 at 0x00007f8fa644d000
RSP=0x00007f8fa749f380 is pointing into the stack for thread: 0x00007f8f70141800
RBP=0x00007f8fa749f3d8 is pointing into the stack for thread: 0x00007f8f70141800
RSI=0x000000000000000c is an unknown value
RDI=0x00007f8f701d2110 is an unknown value
R8 =0x0000000000000000 is an unknown value
R9 =0x0000000000000000 is an unknown value
R10=0x00007f8fc5eb56e0: <offset 0xe006e0="0xe006e0"> in /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/server/libjvm.so at 0x00007f8fc50b5000
R11=0x00007f8fc591af50: <offset 0x865f50="0x865f50"> in /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/server/libjvm.so at 0x00007f8fc50b5000
R12=0x0000000000000000 is an unknown value
R13=0x00007f8f701419d8 is an unknown value
R14=0x00007f8fa749f578 is pointing into the stack for thread: 0x00007f8f70141800
R15=0x00007f8f70141800 is a thread
Stack: [0x00007f8fa73a0000,0x00007f8fa74a1000], sp=0x00007f8fa749f380, free space=1020k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libavcodec.so.52.123.0+0x442060]
</offset></offset></offset></offset>This occurs on different physical instances so chances are pretty low it’s hardware issue. Thanks !
-
mmaldec : correct package buffering accounting
6 novembre 2015, par wm4mmaldec : correct package buffering accounting
The assert in ffmmal_stop_decoder() could trigger sometimes. The
packets_buffered counter was indeed not correctly maintained, and
packets were not subtracted from it if they were still in the waiting
queue.For some reason, this happened especially with VC-1.