# Browser memory exhaustion

**URL:** <https://forum.grid.space/t/browser-memory-exhaustion/2179>\
**Category:** FDM\
**Created:** [October 11, 2024, 12:12pm UTC](https://forum.grid.space/t/browser-memory-exhaustion/2179 "2024-10-11T12:12:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![TechieFenpin](https://forum.grid.space/letter_avatar_proxy/v4/letter/t/dc4da7/32.png) [@TechieFenpin](https://forum.grid.space/u/TechieFenpin)\
**Post date:** [October 11, 2024, 12:12pm UTC](https://forum.grid.space/t/browser-memory-exhaustion/2179/1 "2024-10-11T12:12:03Z")

</div>

Has anyone successfully been able to use Kiri when slicing a large model for 3D printing? I hear that Kiri is great for belt style printers, but I can’t get it to actually export a large file.

I’m working on a CR-30, attempting to print a 200% scale model of [this](https://cults3d.com/en/3d-model/game/articulated-dragon-mcgybeer) dragon. Whenever I attempt to slice the model, the browser eventually reports its run out of memory. This happens with Chrome, Firefox, and Edge. My system has ample memory, and based on my readings, each of these browsers will use however much memory it needs, so RAM as a whole shouldn’t be a problem.

If anyone has been able to get models of this scale to slice successfully, I’d love to hear any tips you may have. Thanks.

---

<div class="post-metadata">

**Author:** ![stewart](https://forum.grid.space/user_avatar/forum.grid.space/stewart/32/21_2.png) [@stewart](https://forum.grid.space/u/stewart)\
**Post date:** [October 11, 2024, 3:59pm UTC](https://forum.grid.space/t/browser-memory-exhaustion/2179/2 "2024-10-11T15:59:31Z")

</div>

Regardless of your system memory, browsers typically limit memory usage to around 3.5GB (the sandbox) – this is a very challenging model with that constraint, so we need to optimize everything that contributes to number of lines/layers output and minimize display niceties.

I happen to have this model lying around from years ago. To get it to slice, I used `0.25` layer height, linear infill at `0.15`, display type to `line`, detail to `25`, and disable `threaded`. The hit `x` to export and bypass slice/preview.

 ![Screenshot 2024-10-11 at 11.56.00 AM](https://forum.grid.space/uploads/default/original/2X/3/32aa3db92013295460a1255a3ae22a47d458aa68.jpeg)

 ![Screenshot 2024-10-11 at 11.55.44 AM](https://forum.grid.space/uploads/default/original/2X/7/7857f4ec6a71a36882f645aa10d2383c37e8e432.jpeg)

---

<div class="post-metadata">

**Author:** ![TechieFenpin](https://forum.grid.space/letter_avatar_proxy/v4/letter/t/dc4da7/32.png) [@TechieFenpin](https://forum.grid.space/u/TechieFenpin)\
**Post date:** [October 11, 2024, 5:09pm UTC](https://forum.grid.space/t/browser-memory-exhaustion/2179/3 "2024-10-11T17:09:43Z")

</div>

Thanks Stewart. That seems to have worked to prevent the issue I was seeing. I appreciate the help.

Unrelated, does Kiri:Moto have the ability to only place supports on the build plate/belt? Most slicers have a setting like that, but I didn’t happen to see it.

Thanks again!

---

<div class="post-metadata">

**Author:** ![stewart](https://forum.grid.space/user_avatar/forum.grid.space/stewart/32/21_2.png) [@stewart](https://forum.grid.space/u/stewart)\
**Post date:** [October 11, 2024, 5:20pm UTC](https://forum.grid.space/t/browser-memory-exhaustion/2179/4 "2024-10-11T17:20:15Z")

</div>

that’s not a feature for “automatic” supports. so you’d have to place supports manually if you need that. certainly I could revisit this. please file a [github issue](https://github.com/GridSpace/grid-apps/issues) so I don’t forget if you think this is important.