![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Heap Management Issues with RiCpp v 7.1 and MS VS 2005? Topic Summary: Created On: 24-Jul-2007 20:38 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have an application that compiled and ran fine when I built it using RiCpp v 7.0 and MS Visual Studio 2003. After upgrading to v 7.1, I've attempted to build and run the app with MS Visual Studio 2005. Now I get "heap overflow" errors almost as soon as the program is executed. The same heap overflow occurs whether I build a release, debug, trace, or animated configuration. Does anyone know of any "known" issues with VS 2005 and/or RiCpp v 7.1 in combination with VS 2005? I've attempted to use the Microsoft linker directive /HEAP:xxx to manually allocate heap at link time, but that hasn't worked. Any suggestions regarding intialization parameters in the Rhapsody OXF / other run time library headers, or any other ideas in general would be greatly appreciated.
|
|
![]() |
|
![]() |
|
Hi,
I don't know if this could be it, but have you rebuilded the oxf libs with the VS2005 compiler? ------------------------- Jesper Gissel Johnson Controls Denmark, Marine Controls |
|
![]() |
|
![]() |
|
Thanks for the reply.
Yes, that was my first step. Any other ideas? |
|
![]() |
|
![]() |
|
FYI: Reverted back to VS 2003. Same problem occurs. Marty Bakal informed me that a change was made to the OXF timer event queue cleanup algorithm sometime after Release 6.1 and before release 7.0. The queue cleanup now has to be performed in user code in situations where lots of timers are executing concurrently and/or many threads are executing concurrently.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.