Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29255 Discussions

Upgrading from Version 9 to Version 10 Causing Mem Usage Problems

aaron_smith
Beginner
483 Views

I have some mixed programing language code (C++/Fortran) which compiles fineusing MS Visual Studio 2005 .NET. I have recently upgraded my fortran compiler to version 10.1.025 from version 9.1. Nowwhen I try to run my release, the memory usage of the codeis out of control. When using Version 9.1, the memory usagewhen starting the code was around 16,000 K.After upgrading, the memory usage of the same code is around 1,800,000 K. The executable is the exact same size in both versions. Has anyone had a similar problem or can anyone suggest any potential fixes? Thanks in advance.

0 Kudos
2 Replies
GVautier
New Contributor III
483 Views

Hello

Typically, memory problems appearing when changing compiler release are symptomatic of programming errors (unitialized pointers, stack corruption, out of bounds array access) especially in mixed langage programming.

So I suggest you to carefully check for this kind of problems before incrimining the compiler.

0 Kudos
aaron_smith
Beginner
483 Views


I did not mean to incriminate the compiler in my previous post. The behavior started upon the upgrade and I was curious if someone else had a similiar problem.

However, I have found the root cause of the problem. It did not reside in my code or the compiler but in a dll that was being called before the code started by windows. The faulting dll was called "wxvault.dll." It was a dll that was used by Dell Embassy Trust Suite that came pre-installed on my computer. When any code was run, the dll was injected and tryed to run. Apparently, the dll does not work well with codes compiled with the new versions of the compiler and is the cause of the memory "bloating" problem that I had. I have removed the program from my laptop and now all of my hybrid codes are now working properly with a correct mem usage.

0 Kudos
Reply