# Galaxy 25.0 ran into javascript heap out of memory error during client installation

**URL:** <https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063>\
**Category:** Uncategorized\
**Tags:** devops-administration, galaxy-local\
**Created:** [July 29, 2025, 1:06pm UTC](https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063 "2025-07-29T13:06:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mariabernard](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/mariabernard/32/6865_2.png) [@mariabernard](https://help.galaxyproject.org/u/mariabernard)\
**Post date:** [July 29, 2025, 1:06pm UTC](https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063/1 "2025-07-29T13:06:10Z")

</div>

Hi there,

I am trying to install the last version of Galaxy (25.0.0) but I encountered an OOM error.

This occure during the client installation. Here are the last log lines:

```auto
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme

<--- Last few GCs --->

[4570:0x57b47c666000] 161066 ms: Mark-Compact 1944.8 (2114.9) -> 1883.0 (2042.1) MB, pooled: 43 MB, 614.41 / 0.00 ms (average mu = 0.765, current mu = 0.739) allocation failure; scavenge might not succeed
[4570:0x57b47c666000] 162116 ms: Mark-Compact 1987.6 (2146.6) -> 1987.6 (2134.3) MB, pooled: 55 MB, 976.70 / 0.00 ms (average mu = 0.581, current mu = 0.070) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

 1: 0x7976359a1c0c node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 2: 0x7976361b6370 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 3: 0x7976361b673a v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 4: 0x7976363c7628 [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 5: 0x7976363ddbe4 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 6: 0x7976363b88a2 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 7: 0x7976363b9706 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 8: 0x79763639a8e9 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
 9: 0x79763638bd8d v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
10: 0x79763638cb34 v8::internal::FactoryBase<v8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle<v8::internal::Map>, int, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::AllocationType) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
11: 0x7976367e8101 v8::internal::FixedArrayBuilder::EnsureCapacity(v8::internal::Isolate*, int) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
12: 0x79763679445e v8::internal::Runtime_RegExpExecMultiple(int, unsigned long*, v8::internal::Isolate*) [/home/maria/miniforge3/bin/../lib/libnode.so.127]
13: 0x7975d5dec776 
Aborted (core dumped)

```

How can I solve this problem?

I installed version 23, 24, 24.2.3 whithout any troubles. (I am testing my tools on different version of Galaxy)

**Environment :**  
Virtual machine : 8Go RAM, 4 CPUs  
OS : Ubuntu 24.04.2 LTS  
conda (version 25.5.1) base environment activated with Python 3.12.9

Thanks for any help you can give me.

---

<div class="post-metadata">

**Author:** ![mariabernard](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/mariabernard/32/6865_2.png) [@mariabernard](https://help.galaxyproject.org/u/mariabernard)\
**Post date:** [July 29, 2025, 1:28pm UTC](https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063/2 "2025-07-29T13:28:56Z")

</div>

Solved!

I just ran

```auto
cd client
make client

```

as suggested in the other log files that redirect to [galaxy/client at dev · galaxyproject/galaxy · GitHub](https://github.com/galaxyproject/galaxy/tree/dev/client) … 🫣

---

<div class="post-metadata">

**Author:** ![sneumann](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/sneumann/32/7708_2.png) [@sneumann](https://help.galaxyproject.org/u/sneumann)\
**Post date:** [September 29, 2025, 7:28am UTC](https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063/3 "2025-09-29T07:28:32Z")

</div>

Hi, same here, and `make client` helped. However, for me not inside `client` but at the top level. I am On branch release\_25.0 end of September 25. Wouldn’t have found it w/o your reply to self. Yours, Steffen

---

<div class="post-metadata">

**Author:** ![warhoofd](https://avatars.discourse-cdn.com/v4/letter/w/df788c/32.png) [@warhoofd](https://help.galaxyproject.org/u/warhoofd)\
**Post date:** [January 13, 2026, 7:38am UTC](https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063/4 "2026-01-13T07:38:45Z")

</div>

Or set/add under :

[`Service]`  
Environment=NODE\_OPTIONS=–max-old-space-size=4096  
(see journalctl for needed value, often \> 2048 MB)  
and  
Environment=GXY\_BUILD\_SOURCEMAPS=0

in your systemd unit file when rebuilding client is triggered by a galaxy start when a update is detected

---

<div class="post-metadata">

**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\
**Post date:** [March 17, 2026, 4:25am UTC](https://help.galaxyproject.org/t/galaxy-25-0-ran-into-javascript-heap-out-of-memory-error-during-client-installation/16063/5 "2026-03-17T04:25:26Z")

</div>


