- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For example, simple code:
program handlesleak implicit none integer(4) :: i do i=1, 100 open(1, file = 'test.txt') write(1,*) i close(1) enddo end program handlesleak
1. Then compile by Visual Fortran Compiler 16.0, set breakpoint on line "open(...)" and look at with "Windows Task Manager" for number of handles. Number of open handles increases step by step.
2. Ok, now compile by previous Intel(R) Visual Fortran Compiler XE 15.0.2.179 and do the same steps. Number of handles does not increase.
Is it a bug of new compiler? And what to do to prevent leaks handles?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, this looks the same as, https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/591225
I will associate your case with the internal tracking id, DPD200375683, to ensure we verify it against any fix.
(Resolution Update on 11/26/2015): This defect is fixed in the Intel® Parallel Studio XE 2016 Update 1 Release (PSXE 2016.1.051 / CnL 2016.1.146 - Windows)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I confirmed this test case is fixed by the Intel® Parallel Studio XE 2016 Update 1 now available from the Intel® Registration Center.

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