Blank Sheet / RAM Exhaustion

Posted by: kavan155gondalia on 17 July 2025, 6:52 am EST

  • Posted 17 July 2025, 6:52 am EST

    Hey team,

    We’ve observed an issue where the sheets content (cells, grid) appears blank, while the ribbon remains visible. This typically occurs when a user’s system has exhausted its RAM.

    We’re looking for a way to detect such ‘crashes’ or instances of the iframe becoming unresponsive due to resource limitations, and then programmatically reload the SpreadJS instance.

    Is there an API or recommended approach for listening to such events and triggering a reload?

    Just for your information, this whole thing is an iframe (if it helps). And we’re confused because it it’s crashing then the whole iframe should crash but we can still see the ribbon of SpreadJS.

    Thanks,

    Kavan

  • Posted 18 July 2025, 2:47 am EST

    Hi,

    SpreadJS is a JavaScript-based application, and JavaScript does not provide a direct event or API to detect when a web application crashes or becomes unresponsive due to resource limitations such as RAM exhaustion.

    However, you can consider using the PerformanceObserver API to monitor performance-related events:

    https://developer.mozilla.org/en-US/docs/Web/API/PerformanceObserver

    This can help detect when the main thread is blocked for extended periods, typically due to high memory or CPU usage.

    Please note that the Designer Component itself is not wrapped in an

    <iframe>
    . If you’re using it inside one, that might affect performance or behavior.

    Performance can also vary significantly based on several factors, including:

    SpreadJS version

    Browser and browser version

    Operating system

    Memory allocation (RAM)

    Processor specifications

    To help us investigate the issue further, could you please provide the sample and file where you’re experiencing the problem? This will allow us to reproduce the issue and assist you more effectively.

    Additionally, please share the following details:

    Operating System informatio

    Memory (RAM) allocation

    Browser name and version

    Processor details

    A sample that replicates the issue

    We look forward to hearing from you. If your sample or file contains confidential information, you can submit it securely through our private support portal: https://developer.mescius.com/my-account/my-support

    Best regards,

    Ankit

  • Posted 20 July 2025, 3:02 am EST

    Hey,

    Here are the details -

    • SpreadJS Version - 17.1.10
    • Browser - Brave (1.80.122)
    • RAM - 16 GB
    • Processor - Intel(R) Core™ i7-14650HX (2.20 GHz)

    I’m sorry I won’t be able to provide a sample file but what I feel is since we’re showing this whole SpreadJS in an iframe of another application and when there are n-number of such applications, these all iframes uses same renderer process and shares memory. So they’re kind of competing for resources and hence the blank.

    Thanks,

    Kavan

  • Posted 21 July 2025, 5:01 am EST - Updated 21 July 2025, 5:06 am EST

    Hi,

    Regarding your concern: “I’m sorry I won’t be able to provide a sample file but what I feel is since we’re showing this whole SpreadJS in an iframe of another application and when there are n-number of such applications, these all iframes use the same renderer process and share memory. So they’re kind of competing for resources and hence the blank.” — this behavior is not specific to SpreadJS. It largely depends on factors such as system RAM allocations, browser performance, and the content used within the designer component embedded in each iframe, as it could increase memory usage.

    That said, I created a sample with 10 iframes, each containing a designer component, and tested it in the Brave browser. It worked as expected without any blank screens. Please refer to the GIF and sample below:

    Gif:

    Sample: Sample.zip

    Tested Environment:

    Brave browser version: 1.80.122

    Ram: 16GB

    Processor: 12th Gen Intel(R) Core™ i7-1270P 2.20 GHz

    SpreadJS Version: 17.1.10

    Since this issue depends on your specific setup — browser, system specs, RAM, and content — if you still want us to investigate further, please provide a minimal working sample or modify the above sample to replicate the issue. This will help us analyze the behavior more effectively.

    Regards,

    Priyam

  • Posted 22 July 2025, 12:15 am EST

    Hey,

    Thanks for investigating on this.

    We’ll let you know if we need more help on this.

    Thanks,

    Kavan

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels