-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Not enough memory on 2.2.1N439 opentx nightly #97
Comments
@brycedjohnson did you download the source or use the release zip file? |
@codecae Release zip file. Should I try the source? |
no the release is the smallest in terms of memory. Which page is loading when you hit the limit? |
On the 4th or 5th page in. Weirdly one time it just worked and I didn't have any issues until I rebooted the taranis. |
That seemed to fix it! Tried it like 3 times and it worked everytime. Thanks! |
Want me to close this issue or want to close it when you reference whatever fix you did? Thanks for the quick help! |
I'd like to leave it open for tracking purposes. Glad it helped you :) @mikeller Looks like the Jenkins build didn't have the -s switch for luac. Should we do an increment release with the current master and include a better build, or should I just update the release zip to contain a build using -s? |
@codecae: No problem, we are still in the process of getting this set up. I would say there have been a couple of pretty significant bug fixes since 1.0, so a release 1.0.1 would be in order. (Also, we should totally move to SemVer (https://semver.org/).) One of the things in SemVer that is sometimes overlooked, but in my opinion is a crucial part of it is
Breaking this rule will create a lot of confusion and frustration amongst users ('I tried v1.0, it did not work, why would I try it again') for no benefit at all (there is an unlimited supply of version numbers, and they are free ;-) ). |
I am not sure if it's the same bug or not, but I am using OpenTX 2.2.0 on a Taranis X9D: Script syntax error I get this with the release 1.1 and the file http://null.eastus.cloudapp.azure.com/job/Betaflight%20Lua%20-%20X7,%20X9,%20X9D,%20X9D+,%20X10,%20X12/24/artifact/obj/*zip*/obj.zip But... i am using FPort :P |
Also disconected but switching between pages I get at the VTX page: Script syntax error |
As a little tip: I am using 2 telemetry scripts, one is the betaflight tx lua scripts and the other one: https://github.com/tozes/taranis_telemetry I am not sure, but maybe betaflight tx lua scripts needs ALL of the available memory. |
@David-VG yes, definitely! but you could use the one-time script (in |
Or just buy yourself a brand new shinny X10: no issue with memory there ;-) |
I dont get Memory errors that way, (running BF.lua manually). But just wanting to warn about the memory issues. Thanks @raphaelcoeffic |
@raphaelcoeffic: Except that the X10 can not (yet) run telemetry scripts at all (as far as I know), and the https://github.com/tozes/taranis_telemetry does not yet support the X10. ;-P |
@mikeller yeah, it's called "widgets", and these scripts will need to be modified. And it still lacks the capability of having widgets that can handle keys. But we're working on it, you can bet on that ;-) |
@raphaelcoeffic: Just hassling you. :-P You are involved in OpenTx? Also, out of interest, what are the MCU / RAM hardware specs of the X10? |
@mikeller I did only a couple of small things. Trying to get more involved these days, so I can make my new X10 with opentx the best TX in the world :-D |
That's a good goal. Having nice new hardware but firmware that isn't as good as the one on the old stuff is always a big disappointment. I've seen flashy marketing videos of FrSky's own firmware on the X10. Is it any good, or is it just a non-recent version of OpenTx with some flashy bitmaps slapped on? |
Totally different. It's quite good for people in need of a UI that basically works like on of the main brands (futaba was named a few times in that context). But it's not my cup of tea when it comes to planes. I would not mind for Quads. probably enough (no LUA though). |
This issue should now be addressed in release v1.0.1. Please download and verify! |
Still out of memory here :( But thanks. |
I'm wondering now if the other script you're using is eating up resources. These scripts have been dialed back and optimized in just about every way possible to reduce the memory footprint. I'm not sure if the other script you're using has undergone the same level of scrutiny. |
Have you tried temporarily disabling the other script and seeing if it still happens? If you attempt this, please power cycle your transmitter to ensure the resources from the previous script are freed. |
It works while using just of both scripts (even if I dont power cycle). Also works if y manually launch BF/bf.lua while the other script is assigned as the only telemetry script. But the other script only runs while being displayed (does not background function, just "run"). https://github.com/tozes/taranis_telemetry/blob/master/X9D/TELEMETRY/telem1.lua As you can see is just a run, divided in 9 functions that just draw the screen. I will try other script just to know if the problem is having 2 telementry scripts or just that "telem1.lua". |
That does not matter at all: it is still kept in memory, as long as you model is loaded and no one-time script is executed. |
Yeah, but it doesent use global variables, just the run loop that just draws. |
The code is stored in memory as well |
Yeah, but only 238 lines. I tought the bitmaps could be the issue but without bitmaps had the same problem. Tried a hello world without issues and also the snake.lua. Will keep trying. |
I use latest 2.2.1. With only lua I had no problem. |
I just now followed exactly what JB's youtube video instructed, and it seems to be working. |
Reopening this to stop users from creating duplicate issues. |
so i noticed after ive already used and exited from the vtx, and pwm menu i can no longer open the script untill rebot because the not enough memory error. This does not happen when using and exiting from the pid, rates 1&2, filters, and rx menu, the next time i open the script it opens to the last menu no out of memory error. |
This issue / pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
Automatically closing as inactive. |
I just downloaded betaflight-tx-lua-scripts v1.0.2 but got the following issue as I was going through (pressing "menu") and when I was on the "Betaflight-RX" page, then pressed "Menu" got this error:
Should I raise a new issue for this? Note that I have:
|
I want to confirm that I have the same issue with same versions above. I did a fresh install of the script. |
I wanted to bring this back up simply to ask if the latest opentx fixes the out of memory issue. I haven't loaded it yet but figured i't ask. I don't see it mentioned in the release notes but wanted to ask before I take the time to upgrade. |
I tested it with opentx-x9d+-noheli-lua-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip and i have the also the out of memory issue |
I also tested it with opentx-x9d+-noheli-lua-en-2.2.2 and BF scripts: bf-tx-lua-1.0.2.zip and have this issue. |
Good morning, I have the same issue as the user Florian Galler. Same Issue, |
I got this working. the change from my previous try is not modifying any files of the scripts. |
Yep worked for me too... great to see not just me! |
@Lazy8onez: Did you recompile the scripts after modifying them? If not, uploading changed source code will force recompilation on the TX, which would explain why this does not work properly. |
I got it also working... my mistake seemed that i used the opentx version without luac... |
@mikeller, no I did not |
@Lazy8onez: My suspicion is that the on-board compilation is less optimised than off-board, so compiling it before installing will have a better chance of working. |
@Lazy8onez: Did you call the luac script by menu (as done by jb on his youtube video) or from the telemetry screen? |
@Snake675 |
I've also got "script syntax error FB/ui.lua: 335 not enough memory" |
I hope this issue will be fixed soon for shure. Some of us seem to have no errors but others do. So what is going on? |
@Snake675: Part of the seemingly inconsistent behaviour that gives some users errors for things that work for others could stem from the 'pick and choose' build on the fly system that OpenTX uses to build their firmware - there are over 1000 possible permutations of the every 'release' of OpenTX that users can install, all of which probably have a different RAM consumption... |
You are correct because usually a build of your own fw on opentx companion
for just Lua script extensin will solve this issue, thats how I solved it
for me. maybe a note or installation instruction on the Lua scripts release
page would probably help...at this point thou this error can still come up
because of what Michael Keller said about many builds
…On Sun, Sep 16, 2018, 6:59 PM Michael Keller, ***@***.***> wrote:
@Snake675 <https://github.com/Snake675>: Part of the seemingly
inconsistent behaviour that gives some users errors for things that work
for others could stem from the 'pick and choose' build on the fly system
that OpenTX uses to build their firmware - there are over 1000 possible
permutations of the every 'release' of OpenTX that users can install, all
of which probably have a different RAM consumption...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#97 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKlVsnhNq6vbJPe8fm_f5S-dXJY15VJ5ks5ubtftgaJpZM4QlQLY>
.
|
@frizzle101101 & mikeller |
Was testing out the latest opentx nightly for a different reason and I saw I was getting a memory error. Seems to happen after paging through a few lua screens.
Script Syntax Error
BF/ui.lua:335
not enough memory
The text was updated successfully, but these errors were encountered: