#5

yeah i’m not able to reproduce just yet.

but, i was only able to find 47 scripts to install :slight_smile:

however… i believe the system command thread is leaking memory, like, quite a lot. will PR a fix. (PR’d.)

just to sanity-check: do you get this crash after a long uptimeor right away after boot?

1 Like
#6

It was right away that I got the crash, I had just booted norns and updated to 191016. I don’t believe that there is a super deep file tree present. I just think that I had perhaps an excessive number of scripts in my code folder as you’d mentioned earlier. Once I removed some of those - it worked just fine and the “scanning” time is unnoticeable/doesn’t hang.

I’m not truly sure whether it’s working since I perhaps coincidentally removed some problematic scripts, but you can see which ones I removed in the email I sent if you’d like to investigate this further. Thanks again for your help!

#7

cool thanks.

yea after looking more i can’t actually get a crash even with the memleak, eventually it goes virtual. so i’ll be curious to look at your code tree. we’ve had one or two other reports of weird behavior with large numbers of scripts and it would be nice to understand them.

#8

What exactly is “scanning” doing?

#9

will get on this right away.

edit: pulled in @zebra’s memory fix and re-uploaded the files.

anyone who has installed can re-run the update by deleting the file /home/we/version.txt (ie, via SFTP or SSH) and re-running the SYSTEM > UPDATE.

please post here if you see further problems.

“scanning” is simply collecting the list of scripts from the dust/code folder. i have a few page-fulls of scripts and it barely blinks on my screen. but importantly, it doesn’t stall out lua, so if you have (for example) a drum sequencer triggering tons of sounds, you won’t get a sync hiccup (and huge smash of noise) when entering the SELECT menu.

1 Like
#10

I just did that and now for some reason my Norns on RPI install won’t start anymore. The screen is not displaying anything and Maiden can’t connect to Matron. That’s strange.
With the previous 191016 update (one hour ago) it was still working (minus a Supercollider fail error that I was trying to solve). I should probably try a fresh install of the whole system.

#11

oh, i know the problem. new files in two minutes.

EDIT: the files have been updated. please try them again. i apologize for the re-upload trouble.

3 Likes
#12

Thanks @Tehn . Quick question, i’ve deleted the version.txt via ftp but is there a command for running the update via ssh ? The screen shows nothing so I can’t run the update directly from the device. Edit: I’ve found it, I’ll download the .tar and run update.sh manually.

Edit: Yep, it’s back, it’s working again. thanks :wink:

1 Like
#13

Installed no problems. I didn’t notice the shutting down message that I think I should have seen from the code. I wonder if extending the sleep prior to shutdown would make sense?

#18

norns didn’t show any available updates after i deleted version.txt, but after powering norns off and on, checking for updates again showed the revised 191016 update, which then installed cleanly from within norns.

#19

Just updated via the norns hardware and, following the on-screen text ‘complete.’, the screen went black and norns is utterly unresponsive (although wifi adapter is lit, and so is the rear status light). First time this has occurred and not sure where to go from here?

UPDATE: approx 30min after first update process, screen came alive again and showed update being available. Followed installation, but now back to a black screen and unresponsive interface. Maiden shows “update complete.” as final line, but I can’t seem to do anything with the hardware.

#20

When the update isn’t complete, press key 3 and the Norns will shutdown. Restart it as normal.

#21

Ahh…many thanks. I thought I had done that the first two efforts, but obviously not.

#22

i would’ve thought any key would’ve shut it down but wow i am sorry. i will fix this.

1 Like
#23

Thanks @tehn. I’m not ruling out a small sprinkling of user error…it’s been one of those days…but it was a new issue in the handful of updates I’ve made.

#24

Hi, there used to be a way to update offline. I can’t seem to find the info for that. Is it still possible to do, and if so how? The wifi settings at my work are a little troublesome.

#25

Curious - the we script directory is not showing up in the script menu after pulling the current (October 23, 2019) norns master branch.

Does anyone with 191016 see this (or not see this) as well?

1 Like
#26

oh, oops. this is on me. i thought the script scanning command was recursing, but i guess not. we doesn’t have any scripts in the top level.

#27

OK - should I github issue that?

#28

fixing it is faster than issuing it

…PR with reversion

4 Likes