PDA

View Full Version : megui 0.3.0.2015 is crashing during encoding, tried 679 and 682 x264 builds


hajj_3
20th September 2008, 18:29
build 979 is crashing, i've sent the bug reports to MS if you can get them off them, just randomly crashes during encoding:( same happens with build 682 so think it might be a megui problem.

hklck516
20th September 2008, 18:42
build 979 is crashing, i've sent the bug reports to MS if you can get them off them, just randomly crashes during encoding:( same happens with build 682 so think it might be a megui problem.


me too .

but use build 965 , no crash problem

i think maybe x264 problem

poisondeathray
20th September 2008, 18:45
r979 works for me (xp pro 32-bit)

Check you CPU temps (e.g. coretemp), reset your overclocks, check your memory with memtest64+

hklck516
20th September 2008, 18:57
r979 works for me (xp pro 32-bit)

Check you CPU temps (e.g. coretemp), reset your overclocks, check your memory with memtest64+



My two PC also have this problem
NO overclock.

PC1 - Intel PD 935 with 2.5GB (vista SP1 64-bit)
PC2 - Intel C2Q 9300 with 6GB ram (vista SP1 64-bit)

hajj_3
20th September 2008, 19:06
do x264 have a fund set up to pay ms for crash logs? if not it might be worth posting on forums asking for donations, im sure coreavc and divx would pay for the money needed.

Adub
20th September 2008, 20:17
Okay, I can also add my confirmation, atleast for build 979. I have not yet updated to the new builds. But what was happening is that it was crashing on the exact same frame every time (17660). The crash log generated by Microsoft claimed x264 as the issue. I will update everything to the latest build and give it a try.


Edit: Bug also confirmed for 982. Same frame again. And I checked the source (a lossless encode of an anime episode) and that frame is one hundred percent fine. Along with the adjacent frames.

Sharktooth
21st September 2008, 04:13
try with 983 (now in the auto-update). it it still crashes, contact the x264 dev reporting the possible bug.

Dark Shikari
21st September 2008, 04:32
1. Microsoft isn't going to do anything, and their bug reporting feature is utterly worthless; the data dumps contain nothing useful at all and might as well be /dev/random.

2. Yes, there's a confirmed bug in x264, but I've only found a few extremely rare cases that can trigger it. I'm waiting on akupenguin to wake up and explain to me why the current code was what it was before I change it, but he hasn't responded to me for almost half a day now, so I'm considering just pushing it in and ignoring complaints...

Edit: Screw it, committed. Thanks to b0bor for sending in the minimal test case necessary to find the bug.

Adub
21st September 2008, 04:40
I have another encode running right now, doing a lossless pass before x264 encoding, and it is setup to run with 983, so I will see if that one crashes.

It is interesting that you say it is rare, as yes, I had one encode run fine in my Queue, and then on the next encode, the crash occured. Both were anime episodes, however they were totally different series, meaning different animation styles and use of b-frames, if that is what is causing the crash (i don't know what the issue is, but it is good to hear that you do Dark Shikari).

This next encode is live action, so I will see if anything happens with it.

hajj_3
21st September 2008, 13:02
maybe you could build in a crash system into x264.exe so that if it crashes it can send a complete detailed crashlog to the x264 developers, quite alot of apps have these nowadays like flashfxp amongst many others.

Dark Shikari
21st September 2008, 13:04
maybe you could build in a crash system into x264.exe so that if it crashes it can send a complete detailed crashlog to the x264 developers, quite alot of apps have these nowadays like flashfxp amongst many others.Impossible unless people build all the x264 builds out there in debug mode, which means no -fomit-frame-pointer, which means significantly decreased performance.

Also, a backtrace is sometimes not possible unless you use --no-asm too (it was in this case).

hajj_3
21st September 2008, 13:29
still crashes with 683 build:(

Dark Shikari
21st September 2008, 13:42
http://i37.tinypic.com/6hkv2u.jpg

still crashes with 683 build:(Bugfix was in 985, not 983... :rolleyes:

hajj_3
21st September 2008, 14:18
ahh, hope its added to megui auto-update soon and i'll try again.

thanks.

Sharktooth
21st September 2008, 17:00
done.

hajj_3
22nd September 2008, 00:10
build 685 fixes the crashing:)

you can close this thread now.

Dark Shikari
22nd September 2008, 00:14
build 685 fixes the crashing:)

you can close this thread now.Its a 9, not a 6 :p

Adub
22nd September 2008, 01:11
Yep, I confirm. My encode worked perfectly!