# Memory Allocation failure

**URL:** <https://verificationacademy.com/forums/t/memory-allocation-failure/30499>\
**Category:** UVM\
**Tags:** Regarding-memory-allocation-of-an-object-in-SV, UVM, questasim, unix\
**Created:** [March 30, 2015, 11:39am UTC](https://verificationacademy.com/forums/t/memory-allocation-failure/30499 "2015-03-30T11:39:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shalem.raju](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/s/ea666f/32.png) [@shalem.raju](https://verificationacademy.com/forums/u/shalem.raju)\
**Post date:** [March 30, 2015, 11:39am UTC](https://verificationacademy.com/forums/t/memory-allocation-failure/30499/1 "2015-03-30T11:39:15Z")

</div>

HI All,

While generating a video format in UVM, I am facing

\*\* Failure: (vsim-4) \*\*\*\*\*\* Memory allocation failure. \*\*\*\*\*

# Attempting to allocate 1073741840 bytes

# Please check your system for available memory and swap space.

Wanted to understand the limitations on the size of the transaction(seq item) should be used.

Currently the transaction item has below fields,  
bit [11:0] y[0:1920][0:1080];  
bit [11:0] u[0:1920][0:1080];  
bit [11:0] v[0:1920][0:1080];

Is this a limitation form UVM or the tool. I am using questasim.

Thanks,  
Shalem

---

<div class="post-metadata">

**Author:** ![dave\_59](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/dave_59/32/4499_2.png) [@dave\_59](https://verificationacademy.com/forums/u/dave_59)\
**Post date:** [March 30, 2015, 3:19pm UTC](https://verificationacademy.com/forums/t/memory-allocation-failure/30499/2 "2015-03-30T15:19:48Z")

</div>

These three items by themselves are 100MB for each transaction. Other things like `uvm\_field\_\* macros and constraints could add much more.

I can’t give you tool specific help in this forum, but a standard debugging technique would be to isolate the exact line of code that is causing the problem. And if it is indeed the construction of a single seq\_item, try pruning fields from that item until you find the culprit.