AviSynth 2.6.0 [May 31st, 2015]

[Groucho2004]

Originally Posted by rean

Groucho2004, I edited "n" to get it working, because it seems to me as a benchmark code for huge frames. A non-edited state gives a memory exception, of course.

Can you post the DLL so we can try it?

Also, did you build the 2.6.0 release code or did you use a current CVS snapshot?

[Groucho2004]

Originally Posted by rean

Groucho2004, /SAFESEH:NO

FYI - Ultim and the other AVS+ developers spent many hours re-writing the exception handling code in Avisynth to make it compatible with new compilers.
IanB is doing the same with Avisynth 2.6.1, check the Avisynth CVS.
Yet, you think they are all wasting their time and a simple linker switch would solve the problem?

[Groucho2004]

Originally Posted by rean

What problem do you mean? Currently it seems I have no issues yet. If you have any real test case that will crash my build or my build will work incorrectly, please post it. Probably this potential issue is long away from my usage. And, I will try the dev version 2.6.1 later, thanks for a point.

Here is some info on one of the issues.
In AVS+, all "new" allocations were checked regarding dependency on returning "NULL" and changed to the non-throwing (std::nothrow) version where applicable.
You can test this by running the script I posted and check the thrown exception. It should look like this:

GetFrameBuffer: Returned a VFB with a 0 data pointer!
size=2123366464, max=2108096512, used=4246732928, free=2113339392, phys=2847870976
I think we have run out of memory folks!

But you're probably just getting something like this:

Evaluate: Unrecognized exception!

The other thing is to implement a way to handle Win32 exceptions (C structured exceptions) as C++ typed exceptions. This can be done by implementing a SEH translator function, that also was done in AVS+.

Yes, your DLL will probably work but it's up to you if you can live with heavily crippled exception handling.

Edit: I just noticed that SEt's modified version does include a SEH exception translator.

[Myrsloik]

This is a less insane version of AVSValue::Assign() in interface.cpp that actually works in both 32 and 64 bit builds:

void AVSValue::Assign(const AVSValue* src, bool init) {
  if (src->IsClip() && src->clip)
    src->clip->AddRef();
  if (!init && IsClip() && clip)
    clip->Release();
  // make sure this copies the whole struct!
  array_size = src->array_size;
  type = src->type;
  string = src->string;
}

I had to fix it when adding my own 2.6 compatibility...

[Fizick]

I tried to recompile C-plugin Yadif with 2.6.0 headers.
GCC and VS compilers detect error in avisynth_c.h with =0 at line:
AVSC_API(int, avs_row_size)(const AVS_VideoInfo * p, int plane=0);
Without =0 compiling is normal.

[Wilbert]

Originally Posted by Fizick

I tried to recompile C-plugin Yadif with 2.6.0 headers.
GCC and VS compilers detect error in avisynth_c.h with =0 at line:
AVSC_API(int, avs_row_size)(const AVS_VideoInfo * p, int plane=0);
Without =0 compiling is normal.

Should be fixed in 2.6.1. Please try.

@rean, your bug should be fixed too in 2.6.1.