Bug #9817

gcc 4_9_2 "internal compiler error" -- memory issue.

Added by Ron Rechenmacher over 5 years ago. Updated over 3 years ago.

Under Consideration
Target version:
Start date:
Due date:
% Done:


Estimated time:


It seems that artdaq demo will not run on a system with less than about 5 or 6 GB of
RAM and 2 GB of swap.

We should think about adding a check for the amount of memory a system has.
On my system, which had 4 GB RAM and 2 GB swap, the OOM (Out Of Memory) monitoring
ended up killing my firefox processes and then g++ also.


#1 Updated by Eric Flumerfelt almost 5 years ago

  • Target version set to 981

#2 Updated by Eric Flumerfelt about 4 years ago

  • Category set to Under Consideration
  • Target version deleted (981)

This is still an issue, and should probably be implemented in We should do some experimentation to determine at about what memory floor issues start to occur, and if there's any dependence on the value of CETPKG_J.

#3 Updated by Eric Flumerfelt over 3 years ago

  • Status changed from New to Resolved
  • Target version set to artdaq-demo Next Release

Doing a clean build of all artdaq packages led to the following line of output:
667.89user 49.71system 4:04.09elapsed 293%CPU (0avgtext+0avgdata 785092maxresident)k
165328inputs+3376400outputs (70major+21085688minor)pagefaults 0swaps

I have added a note to Installing_and_building_the_demo, about recommended minimum specs, and I don't really think there's anything else we can do about this at this time.

#4 Updated by Eric Flumerfelt over 3 years ago

Testing with a virtual machine yields the following result: 1.5 GB of RAM is insufficient, while 2 GB works. This is for a slf6 e14:s46 build using develop (~artdaq v2_02_03).

#5 Updated by Eric Flumerfelt over 3 years ago

  • Status changed from Resolved to Closed
  • Target version changed from artdaq-demo Next Release to artdaq-demo v2_10_00

Also available in: Atom PDF