Run-time error 28, Out of stack space

[indrawn]

Registry Backup 1.6.7
Windows 8.1

Been having this problem with Registry Backup for quite awhile (since before I updated to Win8.1). Whenever the mouse pointer goes over one of the buttons in the RB interface, I get a dialog with the error:

Run-time error '28':
Out of stack space

Just uninstalled, downloaded, and reinstalled, doesn't help.

Screen shot attached.

[Shane]

Very odd. I will load up 8.1 in vmware and see if it happens to me as well

Shane

[Shane]

OK I tried it and it doesnt happen to me.

My windows repair tool uses the same buttons, can you grab it and see if you get the problem there as well?

Shane

[indrawn]

Just installed Windows Repair (All In One) 2.0.1, messed around the interface for a couple minutes, and didn't reproduce the problem.

I don't get it either.

I guess I'll try the portable version of RB.

Thanks, Shane.

[Shane]

That is very odd, the buttons in both of the programs are the same custom control I made, same code and everything for those button controls.

Wait I think I know what it might be. Windows repair is compiled in native mode while the registry backup is compiled in p-code for a smaller size. This also means Windows treats the code differently and it does matter on the CPU.

Native code is bigger exe but a little faster code.

I went ahead and simple recompiled RB in native mode instead, replace the exe you have with this one and let me know if it works better

If it does I will just leave it in native compile on the next update.

Shane

[indrawn]

That RAR'd version crashes whenever I use one of the skinned interface elements (buttons, tabs). Even just putting the cursor over the X caption button makes it crash.

As far as CPU, I have an overclocked Intel Core i7 3970X. That isn't the problem...? I can't believe my system (rated 8.1 by the Windows 8 index) is slower than everyone else's here.

[Shane]

Nothing to do with being slower at all I was just saying that depending how I compile it the CPU treats it differently is all.

SO native mode was even worse, yet WR which is the same controls works fine. Very odd, and I cant get it to happen here.

There are two things you can try to at least help point me in the right direction of what to try next.

1. Try safe mode, this will at least tell me if it is the program on your system or perhaps something else.
2. Would you mind trying with the CPU not over clocked? I use to over clock my CPU and only certain programs would have trouble when I did, this is more of a "lets make sure" type thing and I am just curious

Shane