First, thanks for reading! You are not quite correct though. I have Win 10 Pro and obviously it did not have them pre-installed.

Hm... ok, maybe MS doesn''t ship it with Win10 then. It was installed on all of my Win10 systems though, even on the tablet (which is basically blank as you can't do ...

Any Windows with somehow modern Software on it should be able to load FS VSTs in 32/64bit. The reason is, we are using a "modern" (ehm... 5 years old by now) compiler from Microsoft. This compiler like any older versions of it has a dependency on a runtime DLL (those start with msvcr and followed by ...

yep, but doesn't help much because when there is an exception in the thread, the thread dies and you can't wake the thread up again. You can't catch those exceptions inside the thread because then you won't get any error reporting... everything's a bit shitty.

no, you don't get what this is used for. It basically kill anything that the user put into RubyEdit that takes too long to execute, sleep is a perfect example for this. When you write down sleep in the editor then FS is going to die without this timeout. There won't be any exception, just dead...

3.0.9b1/2 versions support all x86 registers and most of the x86/SSE/SSE2 instructions. Only register you should be carefull with is "ebp" as this is the base address for variables.

There are quite some ways to implement a timeout (like 'break' from a loop, raising an error, etc.)

I haven't found one single other way yet. But Please show me...

call this function (and you're not allowed to alter it at all!!!)
def thisIsBroken
sleep
end

without triggering FS own Ruby ...

Fiber wouldn't work either, the important part is:


this basically gives the code a maximum runtime, and is the only reason why threads are used in the first place.

As a Ruby-ignorant person I have to ask does this really matter if we can just type in -8000 and get the result we want?

You don't want to have the new timeout system turned off when developing in Ruby. eg. if you type in "sleep" in a ruby edit, the whole Ruby interpreter will shut off (on all ...

Well after a lot of digging and trying to find a solution, I'm running out of ideas now. The bug is actually a very old Ruby bug: m

Looks like whenever you use Threads in Ruby, Ruby doesn't bother to cleanup... and its developers don't give a fuck either. This bug report is 2 years old and still ...

The negative number turns of the Ruby Timeout changes that Malc added in 3.0.8
If this works, I have at least an idea where the problem is located. Problem is, on my system I only see a minor Memory creeping, it takes several minutes to increase by 1 MB, so don't expect a fix any time soon...because ...