Constant memory issues using arcade

Arcade Help
1

image
image530×370 5.55 KB

Hi all.
Decided to try to use arcade makecode with my classes this year, because I do not want them to get too used to just scratch.

However, my personal account is constantly struggling to open. I routinely get hit with a memory error problem trying to load the website, both in browser and the app.

I am very baffled by this, as I have only done tutorials, and the only one I have tried modifying more than a little is the text adventure game. Any suggestions would be appreciated, because now I am very worried that the students will have a similar problem.

Thank you,
Mark

2 Likes
2

huh, that’s a new one! @TeachMark how long do you use the website before you see this error? i.e. when this error occurs, how long ago was the last time the page was refreshed or navigated?

also, are you compiling for hardware or mainly developing in the browser? does this only happen when you’re logged in?

2 Likes
3

I’ve seen this happen sometimes too, especially if the page has been open for a while or the editor crashes. Refreshing the page usually helps.

2 Likes
4

Oh - my apologies, I did not answer your questions very clearly.
It is only being developed in the browser, no hardware aims yet. This is being done with 8-10 year olds with minimal practice programing. At most we might use some makey-makey kits as an interface for fun later.
Other things I noticed was that the adventure text game would keep making copies of itself, while saying changes were not synched - I think it was up to 4 when the problems started.
I was using the program for demonstrations probably twice daily for a week, logged in the entire time.

However, because the issue occurs while trying to load the website, I can only say that it seems to have let me get back on when I was logged out, as the way I managed to get back on was to clear my cookies and log in info etc. Though of course, it could be a coincidence that that temporarily solved it - I managed to stay on long enough to demonstrate to one more class for a bit before the error happened again.
While I admit freely I left my laptop on for an extended period of time, the error reoccured after a restart, even with no other programs open other than those that open automatically as part of the organisation (teams, one note etc) so I should not have been too low on ram at that point.

2 Likes
5

Its when I am trying to load into the website or the app. I do not even get to the step of choosing the project I want to work on. I am using a thinkpad with 8 gig of ram, and as said before, the most elaborate thing I have done is duplicated 4-5 functions in the adventure tutorial while changing the text/pictures.

I know this is a very broad problem, so thank you for the help.

2 Likes
6

Step 1: Start Fresh Each Session

  • Before class, close all browser tabs and restart the browser.
  • Open only the MakeCode editor for the current session.

Step 2: Use a Supported Browser

  • Prefer Chrome or Edge — MakeCode performs best there.
  • Avoid using multiple browsers at the same time for MakeCode projects.

Step 3: Manage Projects Carefully

  • Work on one project per browser tab.
  • Avoid duplicating projects unnecessarily; if you must, export a backup first:
    • Click “Project > Download” to save a .mkcd file locally.
  • Limit the number of project copies open at once — 4–5 copies seems to trigger sync issues.

Step 4: Save Frequently

  • Teach students to download their project every 15–20 minutes, especially after edits.
  • This prevents loss if the editor fails to sync.

Step 5: Clear Cache/Cookies if Needed

  • If the editor crashes or loading fails, close the browser, clear cookies/cache, and log in again.
  • This often resolves session-related loading issues.

Step 6: Keep Sessions Short

  • Avoid leaving a browser tab open for hours.
  • Plan short demo sessions (20–40 minutes), then close and reopen the project for the next session.

Step 7: Isolate Classroom Software

  • Close unnecessary programs that run automatically (Teams, OneNote, etc.) if possible.
  • Even though RAM seems sufficient, background software can sometimes interfere with browser-heavy apps.

Step 8: Report Persistent Bugs

  • If the problem persists even after following these steps, document the steps that trigger the issue:
    • Browser type/version
    • Number of project copies
    • Exact error message
  • Send this to the MakeCode team — this helps them identify syncing or loading bugs.

:white_check_mark: Following this workflow should greatly reduce crashes and duplication issues, while keeping student projects safe.

7

I experience problem frequently after the last makecode update, but it seems to only ever happen when I am at home (Where I have a bad internet connection) and I have left makecode running for over 45 minutes. Hope this is of help.

3 Likes