GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — as crash when try to alloc large data · Issue #2827 · AssemblyScript/assemblyscript

as crash when try to alloc large data #2827

New issue
Copy link
New issue
Copy link
Open
#2831
Open
as crash when try to alloc large data#2827
#2831
Copy link
Assignees
CountBleck
Labels
bug

Description

@HerrCai0907
HerrCai0907
opened on Mar 18, 2024
Issue body actions

Bug description

AS compiler crash after hang up a few second.

Steps to reproduce

memory.data(0x7fffffff);

npm run asbuild:debug

AssemblyScript version

v0.27.x

Activity

  1. HerrCai0907
    added
    bug
    on Mar 18, 2024
  2. CountBleck
    self-assigned this
    on Mar 18, 2024
  3. CountBleck commented on Mar 24, 2024

    @CountBleck
    CountBleck
    on Mar 24, 2024
    Member
    More actions

    It looks like most of the time is spent in the allocU8Array call here, but the exception (a simple number, like 2153016872) is thrown in the binaryen._BinaryenSetMemory call without any delay there. I'll look into it a bit more.

  4. CountBleck commented on Mar 24, 2024

    @CountBleck
    CountBleck
    on Mar 24, 2024
    Member
    More actions

    Hm, I can only guess that it has something to do with the copy here, since binaryen.js's memory might hit the 4 GiB limit there.

  5. CountBleck
    added 2 commits that reference this issue on Mar 25, 2024

    Do not allocate MemorySegments for memory.data(i32, i32?)

    This issue will close once commit 373166c is merged into the 'main' branch.
    373166c

    Do not allocate buffers for memory.data(i32, i32?)

    This issue will close once commit 6a89a09 is merged into the 'main' branch.
    6a89a09
  6. CountBleck
    added 4 commits that reference this issue on Apr 3, 2024

    fix: Do not allocate buffers for memory.data(i32, i32?)

    This issue will close once commit 559814d is merged into the 'main' branch.
    559814d

    BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)

    This issue will close once commit ed50aef is merged into the 'main' branch.
    ed50aef

    BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)

    This issue will close once commit 4465767 is merged into the 'main' branch.
    4465767

    BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)

    This issue will close once commit 163a631 is merged into the 'main' branch.
    163a631
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @CountBleck
    CountBleck

Labels

bug

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402520 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.