From: Erik B. <eri...@hi...> - 2017-02-14 09:09:23
|
Thank you Natale, we finally resolved the issue, tracked it down to a version conflict with cmake under Windows which strictly speaking does not seem to be related to Yarp itself. All best, tis 14 feb. 2017 kl 10:00 skrev Lorenzo Natale <Lor...@ii...>: > Hi Erik, > > Can you open an issue on github with this information (and maybe the code > you use to replicate the problem)? > > > > https://github.com/robotology/yarp/issues > > > > it will help us track and other users find it. > > > > Lorenzo > > > > *From:* Erik Billing [mailto:eri...@hi...] > *Sent:* venerdì 10 febbraio 2017 15:50 > *To:* rob...@li... > *Cc:* Haibin Cai <jlc...@gm...>; Fang Yinfeng Fang < > yin...@gm...> > *Subject:* [rc-hackers] Yarp memory issue > > > > Dear list, > > > > we're developing a number of quite complex components using Yarp > 2.3.63 and suddenly ran into what we think are memory related problems. It > appears that a Yarp module may not consume more than about 200 mb of RAM. > When the module tries to allocate more memory than that, it crashes. The > same code running outside Yarp (on the same machine) works fine. > > > > For our setup, we use Windows 7 x64. Components are compiled to 32bit > using VC++ 10. There are no general memory problems on the machine (that > is, lots of free RAM to allocate). > > > > Any suggestions of where to look for solutions are welcome. > > > > Kind regards, > > -- > > *Erik Billing,* > > *Assoc. Senior Lecturer, * > > *University of Skövde* > > *www.his.se/erikb <http://www.his.se/erikb/>* > > *eri...@hi... <eri...@hi...>* > > > > -- > > -- > > Erik Billing, > > *Assoc. Senior Lecturer, * > > University of Skövde > > www.his.se/erikb > > eri...@hi... > -- -- Erik Billing, *Assoc. Senior Lecturer, * University of Skövde www.his.se/erikb eri...@hi... |