|
Post by johnnyd on May 3, 2018 5:16:34 GMT -5
Started having this problem this morning. Only seems to be with LB created programs, but not all.
Googled the problem but nothing relating to LB.
Any help appreciated!
John.
|
|
|
Post by johnnyd on May 3, 2018 5:35:50 GMT -5
OK, found a fix but not ideal. Possibly caused by a recent Windows 7 update but not sure. (Also had ESet antivirus replaced with BitDefender by our IT dept.)
Simply recreated the application as a thought and it worked.
I have several LB progs, so will have to go through then all when I have time to recreate them.
Only just discovered this at work, so not sure if my Windows 10 laptop will do this.
John.
|
|
|
Post by Rod on May 3, 2018 9:13:31 GMT -5
When Carl tried to give us 1gb of memory there were several reports like yours. It was looked into, Liberty requires a contiguous memory allocation. Windows makes this difficult because it randomly allocates memory and finding 1gb on some PCs was impossible. Mine included, until I deleted some programs. To fix the issue Carl went down to 256Mb, more than most folks will ever need. Reports stopped so I assumed that was it fixed. However the problem is even at 256Mb it still has to be contiguous memory. Some virus software may see a program trying to grab large slots of memory as a threat but I would have expected the virus program to have reported the threat. If you have a very busy PC with lots of programs running that may be an issue as well. But you are the first person to report a problem at 256Mb.
|
|
|
Post by johnnyd on May 3, 2018 10:51:42 GMT -5
Hi Rod,
Yes, I remember this being mentioned but it never affected me until now.
The virus checker never batted an eyelid. On the AV interface there is no option to turn it off, so I couldn't try that option.
It is strange that when I rebuilt two or three of the programs that threw up the error initially, the programs worked again, even though it's the same LB I originally built the programs with originally.
There are several background programs (system & IT nosying) that I can't stop.
Oh well, these things are sent to try us!
John.
|
|
|
Post by Carl Gundel on May 4, 2018 10:14:43 GMT -5
What other software do you run? If you have another memory hungry application running, that can contribute to this problem. For example Dragon Systems speech recognition software is known to cause this error.
-Carl
|
|
cundo
Full Member
Muchas Gracias!!
Posts: 146
|
Post by cundo on May 4, 2018 15:00:26 GMT -5
I'm wondering if you had many LB stand-alone programs running in the background John.
|
|
|
Post by Rod on May 5, 2018 3:16:37 GMT -5
Aha! good thinking. Johnny would need to use CtrlAltDel to start task manager and see how many liberty.exe instances are running. If there are several, Johnny needs to find his bug crashing the program. Then let us know if that was the real cause.
|
|
|
Post by Carl Gundel on May 5, 2018 8:35:15 GMT -5
OK, found a fix but not ideal. Possibly caused by a recent Windows 7 update but not sure. (Also had ESet antivirus replaced with BitDefender by our IT dept.) Simply recreated the application as a thought and it worked. I have several LB progs, so will have to go through then all when I have time to recreate them. Only just discovered this at work, so not sure if my Windows 10 laptop will do this. John. Which version of LB are you using?
|
|
|
Post by johnnyd on May 8, 2018 16:12:51 GMT -5
Hi Carl,
4.5.1.
Sorry for the late reply! Been a bit busy.
John.
|
|
|
Post by johnnyd on May 8, 2018 16:18:01 GMT -5
Hi Rod/Cundo
There are no other LB programs or instances of LB running. There may be a couple of large programs running but they have been running in the past with exactly the same LB apps.
Still doesn't explain why rebuilding the offending apps cured them.
John.
|
|
|
Post by Rod on May 9, 2018 14:23:22 GMT -5
Hmm.. did you try the beta at any time? If the last build was using the beta they may have been trying to get 1gb instead of the 256mb that 4.5.1 now uses.
|
|
|
Post by johnnyd on May 10, 2018 3:29:37 GMT -5
Hi Rod,
I did try the beta, but never created programs from it. I'm on 4.5.1 and have used this since it was released properly and this is the version most of my programs are made from now.
One program I regularly update by adding features to was created with 4.5.1 and was fine until last week (03/05) and nothing else had changed (save the Windows update & change of AV).
When rebuilt, it worked OK. However, just ran that same program now and it threw the error. Tried just remaking the .TKN and it still threw the error. Rebuilt it, worked OK.
So what could be different?
John.
|
|
|
Post by Rod on May 10, 2018 6:06:48 GMT -5
Well Liberty is not changing. So if it runs sometimes and not others on a particular PC then memory use on that PC is the culprit. Can you get it to run reliably on other PC's?
I assume here that the program fails to start and gives the error message. When Liberty is unable to get the contiguous memory it needs it just stops and fires off that error.
What is happening (I am no expert) is that Windows starts hundreds of processes when it fires up and your loaded software starts hundreds of background processes. These processes all request memory, Windows allocates virtual memory but spreads it throughout the range of addresses available. Because there are so many small processes this means that it can be impossible to find a contiguous block 256Mb wide. That was the original theory.
Housekeeping the PC to stop any unneeded processes may help. I cured mine by deleting a few bits of software I did not really need on the machine.
So you will need to experiment, first off try different PC's if you can. Do make absolutely sure you are using the very latest download of v4.5.1 to build your exe. If the program is vital you might consider dropping back to v4 which used 70MB.
Let us know how you get on.
|
|
jimh
New Member
Posts: 1
|
Post by jimh on May 19, 2018 23:28:34 GMT -5
When Carl tried to give us 1gb of memory there were several reports like yours. It was looked into, Liberty requires a contiguous memory allocation. Windows makes this difficult because it randomly allocates memory and finding 1gb on some PCs was impossible. Mine included, until I deleted some programs. To fix the issue Carl went down to 256Mb, more than most folks will ever need. When did it change to 256MB? I thought 4.5.1 went down to 768MB
From the 4.5.1 change log: I still provide two options, one using the 4.5.1 runtime and if that fails, I use the 4.04 runtime. It does mean I have had to stay with the 4.04 syntax and avoid the newer functions.
Jim
|
|
|
Post by Rod on May 20, 2018 1:21:21 GMT -5
Sorry, my bad. 256mb was discussed at one point. Folks need to report thsse failures. As it stands only yourself and Johnyd have said they have had trouble. With v4.5.1
|
|