WildernessChild

17th November 2002 15:29 UTC

Crash bug in AVS
This afternoon I was playing around with the Superscope a lot trying to make a dancing 'stick man' and Winamp kept crashing randomly with the error (hope I translate correctly) "The instruction at 0xsomething points to memory at 0xsomething. The read or write operation ("read") on the memory failed.". Then I click OK and Winamp exits.
Until I came to the point where I got this error just after saving my new work-in-progress preset - and now I get it every time I try to open it!
While the error message is on screen the music keeps playing and you can even see the first frame of my stick man in the AVS. But I can no longer continue working on it. Of course I am not happy now :(
I attached the file to this post - please fix this bug soon or tell me how to work around it!

WildernessChild

18th November 2002 11:10 UTC

Hey, where's the file gone?
I don't have it here, might try again this evening (GMT+1).

WildernessChild

4th December 2002 21:00 UTC

Sorry, seems the attachment didn't come through... invalid extension... plz extract after downloading.
And to tell you that the same bug is in 2.78 as well. Should I post it there too?

Rovastar

5th December 2002 15:01 UTC

Yeah it appear to go wrong on WA2 also.

It does appear to be a bug but moving this to the AVS troubleshooting where hopefully someone will find out why it is crashing winamp. Probably exceeding some limits with crazy values or something and needs better validation limit checking.

Once we know why then maybe a fix can be made and hopefully a work around for your code as you should easily be able to get what you want in AVS another way.

dirkdeftly

5th December 2002 19:15 UTC

This only happens when you've exceeded the limits on how many variables you can use. You saved a file where you're using too many variables. There's really no way to fix it, sorry.
We've already added expanded variable support to the wishlist (several times, in fact), but that wishlist has been there for months, and it looks like AVS is going nowhere fast.

UnConeD

5th December 2002 20:30 UTC

The only thing you can do is hex-edit the preset and modify the code to use less variables (note that you need to understand the AVS format for this, unless you make sure the modified code has the same length as the old code).