- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
forgive this perhaps naive question, but I was looking at the CPU usage history diagram available on the task manager app. on Windows machines and noticed that when a fortran executable (a quick-win application with frame window etc. written and compiled/linked with CVF 6.6) starts running, the CPU usage jumps to 100% and stay there for the entire time I keep the executable on. Even if I don't do anything with the executable, no numerical computation is taking place or, in fact, nothing at all is taking place except for the dummy infinite loop that runs in the background to keep the frame window open.
Is this normal? Why would just displaying the frame window suck all CPU resources from a 2.4 GHz Pentium IV?
I feel like something could be fundamentally wrong with some of my settings, but do not know what exactly.
By the way, the program does run fine.
-b.
forgive this perhaps naive question, but I was looking at the CPU usage history diagram available on the task manager app. on Windows machines and noticed that when a fortran executable (a quick-win application with frame window etc. written and compiled/linked with CVF 6.6) starts running, the CPU usage jumps to 100% and stay there for the entire time I keep the executable on. Even if I don't do anything with the executable, no numerical computation is taking place or, in fact, nothing at all is taking place except for the dummy infinite loop that runs in the background to keep the frame window open.
Is this normal? Why would just displaying the frame window suck all CPU resources from a 2.4 GHz Pentium IV?
I feel like something could be fundamentally wrong with some of my settings, but do not know what exactly.
By the way, the program does run fine.
-b.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you modelled your main program after the various samples, there's usually an infinite loop at the end of the main program that simply waits for for termination. This will cause the CPU usage to go to 100%. Insert a call to SLEEPQQ with a .2 second delay in the loop, and things should improve a lot.
Steve
Steve

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page