Personal tools
You are here: Home Forum Use Memory allocation problem in mesh module

Memory allocation problem in mesh module

Up to Use
  • Memory allocation problem in mesh module

    Posted by HAEFFLER_Benoit at November 02. 2007
    I have import a an iges file on Geometry module, i have exploded it to make  groups of shape.

    I import my piece on Mesh module



    I try to mesh it, but Salome return my some error :

    Memory allocation problem
    /dn22/SALOME/series3x/SMESH/DebianSarge/SMESH_SRC/src/SMESH_I/SMESH_Gen_I.cxx : 1166



    My console :

    lfrhab0@lfrpc1519:~$ ./salome_appli_3.2.6/runAppli -k
    Configure parser: Error : can not read user configuration file
    Configure parser: Error : can not read user configuration file
    Searching for a free port for naming service: 2810 - OK
    Lancement du Naming Service runNS.sh > /tmp/logs/lfrhab0/salomeNS.log 2>&1
    Searching Naming Service + found in 0.1 seconds
    Searching /Containers/lfrpc1519/FactoryServerPy in Naming Service +++ found in 1.5 seconds
    Searching /Containers/lfrpc1519/SuperVisionContainer in Naming Service + found in 0.5 seconds
    Searching /Kernel/Session in Naming Service ++ found in 1.0 seconds
    Start SALOME, elapsed time :   3.3 seconds
    additional external python interpreters:  0
    >>> SetSignal( Standard_False ) is not implemented...
    ****************************************************************
    *    Warning: library Component cannot be found
    *    Module will not be available
    ****************************************************************
    ****************************************************************
    *    Warning: library PyCalculator cannot be found
    *    Module will not be available
    ****************************************************************
    th. 3019675328 - Trace /dn22/SALOME/series3x/SMESH/DebianSarge/SMESH_SRC/src/SMESH_I/SMESH_Gen_i.cxx [2368] : SMESH_Gen_i::Load
    th. 3019675328 - Trace /dn22/SALOME/series3x/SMESH/DebianSarge/SMESH_SRC/src/SMESH_I/SMESH_Gen_i.cxx [3283] : SMESH_Gen_i::Load completed
     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

     te4ste: saturation pxyd

     te4ste: saturation letree

    CORBA::LongLong SMESH_Mesh_i::GetMeshPtr() 148991768
    SMESH_Client::SMESH_Client pointeur 148991768
    SMESH_Client::SMESH_Client aMesh 0x8e16f18


    how can i mesh this piece ?
    • Re: Memory allocation problem in mesh module

      Posted by Christophe Bourcier at November 02. 2007
      Hi

      You can decrease the number of elements you want in your mesh.

      Or add a swap file to increase the amount of memory available. For instance, to create a 2Go swap file on /opt:

      dd if=/dev/zero of=/opt/memory.swap bs=1024 count=2000000
      mkswap -c /opt/memory.swap 2000000
      sudo swapon /opt/memory.swap

      Cheers
      • Re: Memory allocation problem in mesh module

        Posted by HAEFFLER_Benoit at November 07. 2007
        thanks Christophe for your answer

        I have not many freespace on /opt.
        But i have a swap disk to on my system
        /dev/sda2            2833        3075     1951897+  82  Linux swap / Solaris
        how can salome use this swapdisk ?

        Benoit

        • Re: Memory allocation problem in mesh module

          Posted by Christophe Bourcier at November 07. 2007
          Hi

          Salome uses your swap partition through your linux operating system, as set in /etc/fstab.

          The solution I gave allows you to add to your OS another swap space, using another hard drive or an usbkey.

          If you don't have any of them, you will have to change the hypotheses of your mesh to reduce its number of elements.

          Christophe
          • Re: Memory allocation problem in mesh module

            Posted by HAEFFLER_Benoit at November 07. 2007
            When salome crash

            The processus "Salome_session_server" has use :
            - 3Go of virtual memory
            - and only 81.9Mo of swap

            the virtual memory was used at 92 %
            and the swap was only use at 11%


            • Re: Memory allocation problem in mesh module

              Posted by HAEFFLER_Benoit at November 07. 2007
              I have test with an other algorithme (netgen 3d) and salome return me :

              th. 3019638464 - Trace /dn22/SALOME/series3x/SMESH/DebianSarge/SMESH_SRC/src/SMESH/SMESH_subMesh.cxx [1626] : NETGEN_3D failed on subshape 1 with error COMPERR_OCC_EXCEPTION "SIGSEGV 'segmentation violation' detected. Address 8374efe0"
Powered by Ploneboard
Document Actions