Audacity Forum

justinrpg wrote:

steve wrote:

justinrpg wrote:the limitation of a 32bit OS is NOT 3GB!!!

We probably don't need all of the "!!!"
To clarify the situation, see here: http://msdn.microsoft.com/en-us/library ... ory_limits

that link leads to "unable to fulfill service request" error message!!!

Not on my system, it doesn't! [note the single "!" !]

I raised this post and the problem is Audacity Freeze with audio cache enabled.
I did not bother replying to the memory limit originally asserted because:-
i) My system only has 2GB
ii) My Win7 system was using around 300-500MB of RAM so there was oddles to do whatever Audacity required
iii) Recording at 24/192, takes around 20 minutes to crash, i.e. all RAM fully utilised
iv) I thought it was irrelevant to the problem of the post.
I still think the amount of RAM fitted to the mother board is irrelevant to the problem of the post however, as you cannot read the link, allow me to assist:-
Version Limit on X86 Limit on X64
Windows 7 Ultimate 4 GB 192 GB
Windows 7 Enterprise 4 GB 192 GB
Windows 7 Professional 4 GB 192 GB
Windows 7 Home Premium 4 GB 16 GB
Windows 7 Home Basic 4 GB 8 GB
Windows 7 Starter 2 GB N/A
Apologies for not being able to format as a table
Have a nice day

justinrpg wrote:

audino wrote:With your system Win7 x32 you can install max 3GB of ram so it might still not enough for your set up.
That is a limitation for the 32bit system unless you upgrade (install from scratch new OS) to 64bit.

that is not true, I have a 32bit Windows 7 ultimate and 4GB of ram... it allows me to use 4GB of ram on a 32 bit operating system!!! the limitation of a 32bit OS is NOT 3GB!!!

You can install 4 GB of RAM but perhaps what audino means is that the maximum address space of any 32-bit application like Audacity is 3 GB. And for Audacity as we distribute it, it's 2 GB because we don't set IMAGE_FILE_LARGE_ADDRESS_AWARE to yes (and even if we did, the user would have to set the 4-gigabyte tuning (4GT) feature for Audacity themselves thus:
http://msdn.microsoft.com/en-us/library ... 85%29.aspx ).

When I was crashing on editing yesterday with Audio Cache on, I would of course have been very close to that 2 GB limit, though that doesn't excuse the crashes.

If Dennis wants to try a build with IMAGE_FILE_LARGE_ADDRESS_AWARE set to yes and enable 4GT for himself, I could make such a build as an experiment, though I don't see why it would help crashes when Audacity isn't using anything like that amount of RAM, which I think is true for Dennis.



Gale

steve wrote:

Gale Andrews wrote:Can you give your exact steps in View History?

1. View > History
2. Discard

Yes, obviously but I meant exactly what item in the list are you selecting before you discard?

Are you still saying:

1 Generate 30 minutes mono 44.1/32
2 You now have d00 and d01
3 Undo
4 You still have d00 and d01
5 Generate another 30 minutes mono 44.1/32
6 You now have d00, d01, d02

leaves you with d00, d01 and d02 at step 6? If so, was this with audio cache on or off?

I don't like it when our favourite program does different things on different machines.


Gale

Gale Andrews wrote: leaves you with d00, d01 and d02 at step 6?

My mistake. Nautilus shows d00, d01 and d02, but if the view is refreshed when step 5 (generate the new 30 minute track) is completed, d00 disappears leaving just d01 and d02.

@Gale:

If Dennis wants to try a build with IMAGE_FILE_LARGE_ADDRESS_AWARE set to yes and enable 4GT for himself, I could make such a build as an experiment, though I don't see why it would help crashes when Audacity isn't using anything like that amount of RAM, which I think is true for Dennis.

Of course I will assist. I would be only too pleased to assist but I do not see what benefit this could be when I only have 2GB of RAM in either of my systems. Just advise me as to how you would like to proceed and I will try to assist.
I also believe Audacity is only using large amounts of RAM when I have the audio cache enabled and the reserved RAM set low, i.e under 16MB in XP and under 100MB in Win7.

otwo_pipes wrote:@Gale:

If Dennis wants to try a build with IMAGE_FILE_LARGE_ADDRESS_AWARE set to yes and enable 4GT for himself, I could make such a build as an experiment, though I don't see why it would help crashes when Audacity isn't using anything like that amount of RAM, which I think is true for Dennis.

Of course I will assist. I would be only too pleased to assist but I do not see what benefit this could be when I only have 2GB of RAM in either of my systems.

Indeed, though since the Audio Cache feature does not behave correctly on some machines it is not completely inconceivable that setting large address aware could make a difference; for example if there was some coding oversight that assumed this flag was set.

But if someone joins the discussion who has 4 GB system RAM or more obviously that is a much more interesting case to test. Making more tests myself is not a priority right now given the feature is to be hidden.



Gale

But if someone joins the discussion who has 4 GB system RAM or more...........

Okay, if we both put this one on the 'back burner' when I upgrade my desktop we can revisit the issue.