Memory usage begins at around 700 MB and gradually rises to nearly 2GB. I close and reopen B4J once in a while to remedy that. I think it's a memory leak, but I've never managed to find and cure it.What is the memory usage (check with task manager)?
The first thing that I would have done is to take 100 of these modules and make them a b4xlib. It is very simple to do and it will help.
Sure, that's the direction:Could you point me in the right direction? Thanks a lot.
Hi Erel.The IDE will soon be a 64 bit process. This will help with the memory usage as it will allow the IDE to consume more than 2gb or RAM.
It will help in this case.
I'm afraid that is a bit ambiguous - it could mean that you will just keep the present current versions available as 32 bit or do you intend that both 32 and 64 bit versions will be released for all future versions?The latest 32 bit version will also be available for download.
Well, my understanding is that new versions will be in x64. There will be a link to the last x86 build. Anyway, I believe that in long term we will have to use the x64 ide. Most computers today are running x64 windows.I'm afraid that is a bit ambiguous - it could mean that you will just keep the present current versions available as 32 bit or do you intend that both 32 and 64 bit versions will be released for all future versions?
Exactly.Well, my understanding is that new versions will be in x64. There will be a link to the last x86 build. Anyway, I believe that in long term we will have to use the x64 ide. Most computers today are running x64 windows.
I gave the idea a try. Unfortunately, I couldn't use a normal (compiled) library, since my modules are very interdependent and 90% of them have their own layouts. I tried b4xlib. It does work, but has no effect on memory consumption and speed, which is no surprise as the library code is still present and active.The library idea is exactly what I was looking for! a way to lighten the load. That would be great! and if I need to change part of it I can always edit the library.
There will be a link to the last x86 build.
Sorry about being pedantic but this is still ambiguous in colloquial British English. It could mean that either the x86 build will always be (say) B4A v11 or it could mean that the x86 version is of the latest x64 version.Exactly.
I can't see Erel clarifying that anywhere. You may 'believe' it but as I have pointed out up to now all the statements are ambiguous.According to the explanations given, I believe "the last x86 build" means "the final one".
I don't mean to drag the conversation on, but just to clarify, the "I believe" part was just a habit I picked up from essay writing. What amykonio stated clearly signifies that there won't be x86 updates after a certain version, and Erel responded with "Exactly", which, well, is a perfect indication that he has verified the previous statement.I can't see Erel clarifying that anywhere. You may 'believe' it but as I have pointed out up to now all the statements are ambiguous.
Sorry but it doesn't. The Chambers dictionary definition of 'last' isWhat amykonio stated clearly signifies that there won't be x86 updates after a certain version
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?