Log in

View Full Version : megui: process exits with error code 1073741819


autoimmune
11th August 2011, 19:17
I have been trying to back up my collection of blu-ray disks with megui and avisynth filters. My set up is Ubuntu 11.4 as my main OS with megui running in a windows XP virtual box. I started an encode of THE SOCIAL NETWORK and megui ran fine for about 5 days and then about 4 hours before completion it throws me the error code in the title of this thread.
i believe the version of megui im using is 2028.
Here is my log file:

--[Information] [8/4/2011 9:57:26 PM] Started handling job
--[Information] [8/4/2011 9:57:26 PM] Preprocessing
--[Information] [8/4/2011 9:57:26 PM] Avisynth input script
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #resize
---[NoImage] #denoise
---[NoImage] vaguedenoiser (threshold=0.5, chromaT=0.5, nsteps=12)
---[NoImage] undot()
--[Information] [8/4/2011 9:57:26 PM] Job commandline: "MeGUI_2028_x86\tools\x264\x264.exe" --crf 18.5 --bframes 16 --b-adapt 2 --ref 16 --rc-lookahead 60 --merange 64 --me umh --subme 10 --partitions all --trellis 2 --sar 1:1 --output THE_SOCIAL_NETWORK\BDMV\STREAM\00011.mp4"
THE_SOCIAL_NETWORK\BDMV\STREAM\00011.avs"
--[Information] [8/4/2011 9:57:26 PM] Encoding started
--[Error] [8/11/2011 7:04:08 AM] Process exits with error code: -1073741819
--[Information] [8/11/2011 7:04:09 AM] Standard output stream
--[Information] [8/11/2011 7:04:09 AM] Standard error stream
---[NoImage] avs [info]: 1920x1080p 1:1 @ 24000/1001 fps (cfr)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Slow SlowCTZ
---[NoImage] x264 [info]: profile High, level 5.1
--[Information] [8/11/2011 7:04:10 AM] Job completed

i have searched google and many people seemed to be having this problem with multiple applications. They were saying it was an access violation, but no one seemed to be offering a solution. I have 1000 megabytes of ram and one cpu core alloted to the virtual machine. If anyone could help with this i would be very grateful.
Edit' I had managed to complete an encode to mp4 of the exact same movie in handbrake, but discarded it when i discovered how terrible handbrakes denoise function was.

IanB
11th August 2011, 22:26
-1073741819 decimal is 0xC0000005 in hex, which is "Access Violation".

It probably would help to paste the contents of the script "THE_SOCIAL_NETWORK\BDMV\STREAM\00011.avs" so we know what plugins are involved. And of course tell us what and whose version of Avisynth you are running.

Groucho2004
11th August 2011, 23:34
-1073741819 decimal is 0xC0000005 in hex, which is "Access Violation".

It probably would help to paste the contents of the script "THE_SOCIAL_NETWORK\BDMV\STREAM\00011.avs" so we know what plugins are involved. And of course tell us what and whose version of Avisynth you are running.

If any of the megui developers are reading this - Look up "FormatMessage()" in the Win32 API documentation. It allows to format the error message thrown by "GetLastError()" in readable form. Dumping a signed int into the log is not very helpful.

Also, pulling the version info from avisynth.dll is just as trivial.

autoimmune
12th August 2011, 03:37
the contents of the script are in the log message starting at the 4th line of the log and ending where it says undot(). The only thing that script does is apply vague denoiser and undot, the rest are just the standard crap that megui throws in. The version of avisynth according to an .avs file i created with the line "version()" in it... is 2.6, build sept 7th 2009.
' I beleive Ben Rudiak Gould is the "whose" that you may be looking for, IanB.

IanB
12th August 2011, 06:05
2.6 Alpha 2, 2.6.0.1, was built Sep 27, 2009 [18:39:23], is this the version you are running?

...
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] #resize
---[NoImage] #denoise
---[NoImage] vaguedenoiser (threshold=0.5, chromaT=0.5, nsteps=12)
---[NoImage] undot()
...This does not count as the script, it has no source statement to begin with. I am not here to guess what might or might not be, if you want help, meet me halfway and provide the information I asked for and please do it accurately.

autoimmune
12th August 2011, 06:13
I found that a similar error can be fixed by using the command "setmemorymax" with the avisynth script. I increased the memory alloted to my virtual machine to 1500 megabytes and used a program called "freeramxpPro" to determine how much ram i had that was actually free. It turns out it was about 1100 megabytes free so i added the line "setmemorymax(1000)" to my avisynth script. I guess we will know in a couple of days whether or not this fixed my issue but any help in the mean time would still be much appreciated.
'just saw your reply IanB, hold on a sec and i will post the full script.

autoimmune
12th August 2011, 06:21
LoadPlugin("C:\Documents and Settings\myusername\Desktop\MeGUI_2028_x86\tools\dgavcindex\DGAVCDecode.dll")
AVCSource("C:\Documents and Settings\myusername\Desktop\THE_SOCIAL_NETWORK\BDMV\STREAM\00011.dga")
#deinterlace
#crop
#resize
#denoise
vaguedenoiser (threshold=0.5, chromaT=0.5, nsteps=12)
undot()

This is the .avs file i loaded into megui and then pressed the enqueue button.
and yes that is the version of avisynth i am running
also for the ultra-curious "myusername" is not the folder that i have sitting between documents and settings and desktop. It is actually something quite vulgar and i edited it out of respect.

IanB
12th August 2011, 23:20
You should try AVS 2.6.0 Alpha 3 [110525] (http://sourceforge.net/projects/avisynth2/files/AviSynth_Alpha_Releases/AVS%202.6.0%20Alpha%203%20%5B110525%5D/) it fixes quite a few bug present in Alpha 2.

Also if you are exhausting the 2GB address space then you should SetMemoryMax() to a lower value, typically 256, 128 or even 96. This will constrain the maximum size of the Avisynth frame cache and leave more available for other purposes, it does not control any other malloc usage by filter, plugins or the host application itself.

It might be advantageous to use one of the older piping methods to feed the script output into x264, this allows x264 and Avisynth to run in 2 separate processes each with their own 2GB address space.

autoimmune
13th August 2011, 01:54
I will definitely upgrade to alpha 3, as i thought i had the most modern version already. I will have to try out setmemorymax() at a low value, although i remember when i used to play with the mc_spuds script that setting setmemorymax() too low would cause the script to slow down(even more), so i will just have to experiment.

I'll report back when my blu-ray encode either completes or crashes. Megui estimates the completion time at about 6 days, so i guess we will see. Thanks to IanB and Groucho2004 for your input so far.

autoimmune
19th August 2011, 03:31
ok... i think i am losing my mind. My last attempt at encoding the social network threw the same error code at the end, again. I am doing a complete reinstal of megui and avisynth, and i am also setting setmemorymax(128). The thing is, when i check what .dll is in my system32 folder, it reports 2.6.0.2. It is the newest one i can find, no matter what version i can get ahold of. The punchline is, whenever i try to run an .avs script with "version()" in it, with a program called SUPER, it reports i have a version from 2009, and when i check the win32 folder after running SUPER, the .dll reports being 2.6.0.1! I have uninstalled SUPER. And now i have the latest 2.6.0.2, and i am going to let the encode try again.

'edit
and i just had another idea. i am turning the quality setting all the way down so i can see if i can finish the encode at any setting and get a result faster

Floatingshed
19th August 2011, 07:53
In my experience this error is always memory related. I think there must be a memory leak somewhere as it is almost always resolved by a reboot. I've lived with this irritation for months, nobody seems to have a real solution.

autoimmune
3rd September 2011, 03:05
i apologize for not responding for so long. I have been unable to find a solution. I have come to the conclusion that trying to run a somewhat buggy scripting language within a somewhat buggy gui within a ten year old operating system within an open source virtual machine on top of ubuntu is probably a bad idea. i have switched to handbrake for now until i can try and see if avisynth will work better within vmware.