Log in

View Full Version : mencoder/x264 referenced memory fault


morph166955
4th January 2007, 19:11
I'm getting a weird error when using x264 with mencoder.

The instruction at "0x00a5343a" referenced memory at "0xffffffff". The memory could not be "read".

I'm encountering this issue on several different builds of mencoder, both ones I've made using mingw & gcc 4.3.0 that are optimized for the core2 (tested both with and w/o pthreads). I've also tried to use celtic druids most recent prescott build (from 12-20-06) and it fails the same way although the instruction changes which it obviously would being that the executables are different.

The reason I'm posting this here is that every other codec I have tested (fmp4 via lavc and xvid) have worked perfectly. infact ive used the fmp4 probably a good 30 times on this system with no problems at all.

I've tested this on 3 different sources including ones that worked with fmp4/lavc successfully so i dont think that the source is bad, nor do i think that mencoder is having an issue with the files.

I get that error about 4-5 frames into the encode.

Anyone got any ideas? I have a good pile of things i want to encode to x264 and this is buggin the hell outa me!

Thanks in advance

DarkZell666
4th January 2007, 21:48
Sirber had a problem recently with memory faults too, trying to encode audio to wav (nothing to do with intensive video processing :p).

In your case, did you try the vanilla build (the Generic runtime detection version: http://esby.free.fr/CelticDruid/mirror/mplayer/mplayer2006.12.20.7z) ?

morph166955
4th January 2007, 23:00
thats next on the list...im finishing up a backup routine for something i was doing yesterday and thats next on the list.

morph166955
9th January 2007, 21:43
sorry for the delay...had some things goin on

i just ran it on celtics 12/20 build that has cpudetect compiled into it, again failed. similar error, just a different memory address that it failed at (0x00a0f0ca incase anyone is curious and wants to look).

any more ideas to try?

morph166955
9th January 2007, 23:42
in an attempt to further help someone diagnose this, here is the last lines that mencoder outputs when run with -v -v. I just compiled this binary as well as x264 so its as up to date as i can get it (x264 @ r617, mplayer @ r21859). This build crashes at 0x00a57c8a if that helps.


VDec: vo config request - 960 x 528 (preferred colorspace: Planar YV12)
Trying filter chain: expand x264
vo_debug: query(Planar YV12) returned 0x0 (i=0)
vo_debug: query(Planar I420) returned 0x403 (i=1)
VDec: using Planar I420 as output csp (no 1)
Movie-Aspect is 1.82:1 - prescaling to correct movie aspect.
VO Config (960x528->960x528,flags=0,'MPlayer',0x30323449)
REQ: flags=0x3 req=0x0
using IPB
get_path('subfont.ttf') -> 'c:/Program Files/mplayer/mplayer/subfont.ttf'
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities MMX MMXEXT SSE SSE2
New_Face failed. Maybe the font path is wrong.
Please supply the text font file (~/.mplayer/subfont.ttf).
subtitle font: load_sub_face failed.
OSD chg: 3 V: no pb:-1
OSD chg: 2 V: no pb:-1
*** [x264] Allocating mp_image_t, 960x528x12bpp YUV planar, 760320 bytes
(imgfmt: 30323449, planes: 02600020,0267BC20,0269AB20 strides: 960,480,480, chroma: 480x264, shift: h:1,v:1)
*** [expand] Direct Rendering mp_image_t, 960x528x12bpp YUV planar, 760320 bytes
(imgfmt: 30323449, planes: 02600020,0267BC20,0269AB20 strides: 960,480,480, chroma: 480x264, shift: h:1,v:1)
Pos: 0.0s 1f ( 0%) 0fps Trem: 0min 0mb A-V:0.000 [0:0] A/Vms 1/0 D/B/S 0/1/0
vd_ffmpeg data: b6010000, 27c0052, ffffffbf, ffffffff
using IPB
OSD chg: 3 V: no pb:-1
OSD chg: 2 V: no pb:-1
*** [x264] Allocating mp_image_t, 960x528x12bpp YUV planar, 760320 bytes
(imgfmt: 30323449, planes: 026C0020,0273BC20,0275AB20 strides: 960,480,480, chroma: 480x264, shift: h:1,v:1)
*** [expand] Direct Rendering mp_image_t, 960x528x12bpp YUV planar, 760320 bytes
(imgfmt: 30323449, planes: 026C0020,0273BC20,0275AB20 strides: 960,480,480, chroma: 480x264, shift: h:1,v:1)
OSD chg: 3 V: no pb:-1
OSD chg: 2 V: no pb:-1

nm
10th January 2007, 06:34
in an attempt to further help someone diagnose this, here is the last lines that mencoder outputs when run with -v -v. I just compiled this binary as well as x264 so its as up to date as i can get it (x264 @ r617, mplayer @ r21859). This build crashes at 0x00a57c8a if that helps.
Compile with debugging symbols and use gdb to analyze the problem (http://www.mplayerhq.hu/DOCS/HTML/en/bugreports_what.html#bugreports_crash). If you want to get it fixed, read the whole documentation on how to report bugs (http://www.mplayerhq.hu/DOCS/HTML/en/bugreports.html) and post to the appropriate mailing list.

morph166955
10th January 2007, 07:42
the reason i posted it here is because i believe it may be an issue with x264 itself as opposed to mplayer/mencoder. the reason i believe this is that the only codec that has a problem in mencoder is x264. mplayer is able to play all the 264 media that i have encoded in the past so i dont think it has anything to do with the decoding side which i believe is done internally. should it turn out to be a bug with mencoder i will file the appropriate bug reports and everything else attached to that, but before i do i want to rule out x264 (or more specifically its library that mencoder uses when it builds itself) as the cause.

nm
10th January 2007, 08:51
You can verify the source of the problem only by debugging MEncoder. Also remember to build the x264 library with debuggin symbols enabled.

Sharktooth
11th January 2007, 01:54
if you're on windows please use those mplayer/mencoder builds:
http://oss.netfarm.it/mplayer-win32.php
and verify if the problems persist.

morph166955
11th January 2007, 19:49
just tested using "mencoder-p4-svn-21847.7z" from that site. problem still exists. this time it fails at 0x00a7708a when on x264, no issues on lavc or xvid using same source files.