Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for WebAssembly
  4. RangeMemory: could not allocate memory on startup
QtWS25 Last Chance

RangeMemory: could not allocate memory on startup

Scheduled Pinned Locked Moved Unsolved Qt for WebAssembly
2 Posts 2 Posters 69 Views
  • 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.
  • C Offline
    C Offline
    Caro
    wrote on 10 Apr 2025, 08:01 last edited by
    #1

    Hello,
    As a team we are developing embedded application in Qt/QML 5.15.18 for HMI display. We are also releasing this application as a WASM build for internal team as a customization version.
    The problem is that when we run/open WASM version in browser we get sometimes this error
    b8041c5b-0d5b-47b4-a9f6-592427dd37f3-image.png
    It actually occurs only when application is starting, we never get this error in runtime when app started without issues. Reproduction is around 1%-2% so it is hard to investigate. My biggest problem is that I don't know how to analyze this exactly. I don't know if his is error from the C++/emscripten/javascript code or any other area. And what tools to use to debug this memory issue in browser.

    J 1 Reply Last reply 10 Apr 2025, 08:23
    0
    • C Caro
      10 Apr 2025, 08:01

      Hello,
      As a team we are developing embedded application in Qt/QML 5.15.18 for HMI display. We are also releasing this application as a WASM build for internal team as a customization version.
      The problem is that when we run/open WASM version in browser we get sometimes this error
      b8041c5b-0d5b-47b4-a9f6-592427dd37f3-image.png
      It actually occurs only when application is starting, we never get this error in runtime when app started without issues. Reproduction is around 1%-2% so it is hard to investigate. My biggest problem is that I don't know how to analyze this exactly. I don't know if his is error from the C++/emscripten/javascript code or any other area. And what tools to use to debug this memory issue in browser.

      J Offline
      J Offline
      JonB
      wrote on 10 Apr 2025, 08:23 last edited by
      #2

      @Caro
      You might start by Googling webassembly memory () could not allocate memory and read through the other reports and comments.

      1 Reply Last reply
      0

      1/2

      10 Apr 2025, 08:01

      • Login

      • Login or register to search.
      1 out of 2
      • First post
        1/2
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved