Welcome to the Pycom forum Forum
    • \[\[global:header.categories\]\]
    • \[\[global:header.recent\]\]
    • \[\[global:header.tags\]\]
    • \[\[global:header.popular\]\]
    • Login

    Explore Pybytes | Official Documentation | Report a Firmware Bug/Issue | GitHub

    MemoryError: memory allocation failed, allocating 1348 bytes

    Scheduled Pinned Locked Moved Discussion
    3 Posts 2 Posters 211 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      snehasg96
      last edited by

      Dear Community,

      I think I ran into this issue after carrying out extensive computation by establishing bidirectional communication between the lopy nodes. I copied the code to the SD card, but don't understand how the computation would occur externally.

      Any suggestion on how to rectify this?

      Note: When I mean computation I am just using the API call to get the SNR within the infinite while loop and receive data from the transmitter and creating lists to store what needs to be sent back to the transmitter. (I even tried reducing the number of lists used for solving this issue.

      Any feedback will be really helpful. ( I am using LoPy 3)

      C 1 Reply Last reply Reply Quote 0
      • C Offline
        crumble @snehasg96
        last edited by

        @snehasg96

        without details we can only tell you to reduce your memory allocations ;)

        Check if you really need that much RAM or if you have a memory leak. If you really need that much, store the huge data on SD card. Call GC before allocating huge chunks. Avoid stuff which fragments your RAM. Avoid floats, with statments for locks, string methods and such stuff.

        S 1 Reply Last reply Reply Quote 1
        • S Offline
          snehasg96 @crumble
          last edited by

          @crumble Hi thank you so much for your input. By details would posting my code help narrow down on what is happening?

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post

          Pycom on Twitter

          Pycom