I have an app built with 2009 Release 2.1. In the app I do some ram image stuff and the code at the time could not go over 4 gb ram due to an internal bug in Realbasic.
I tried doing some googling to find out what future version beyond that that fixed the issue but could not find anything on it. I need to upgrade this to the version that resolves this but not sure which one it is.
Does anyone have an idea?
Thanks,
Tom
Until 64bit builds are available, I don’t believe any Xojo-built app can address more than 4GB of ram.
But I’ve been known to be wrong before… 
Kimball is right except that, currently, your app won’t actually be able to address the full 4GB.
See https://forum.xojo.com/2843-performance-issues-between-windows-versions/40
I don’t mean actually accessing 4gb of ram at a time. The app actually makes an image of the ram contents itself. The app was originally done by someone else and in the code where the image stuff is done was this comment:
// Currently we crash with a blue screen if we try to image more than 4gb of memory. We'll prevent this from happening until
// we can get an official fix for the crash.
'if offset + readBytes > 4294967295 then// 4gb minus 1 byte
Then uncommented it was using 3.2gb. I thought some time back I had read about an issue with the framework where there was a bug preventing more than 4gb of ram or something. I just cannot recall exact details.
Thanks.
It’s not a Xojo bug at all, it’s a limitation because of the fact that Xojo currently builds 32-bit apps. 64-bit should hopefully arrive next year.
The app can use, in total, more more than 4 Gb MAX.
This includes the code that is the app, and all the data.
This limit may be lower on certain versions of Windows so you may be limited to something less than 4Gb
That is the built in limits of a 32 bit process.
Nothing we can do until Xojo creates 64 bit applications.