 |
| Stephen Brooks 2007-08-21 14:16:05 | I just noticed my copy of v4.43d running here had 80`000 Windows handles open, looks like leak but I'd not noticed it before. Anyone else have this problem, or could it just be an intermittant oddity? |
| Xanathorn 2007-08-21 14:56:21 | My clients have 5.500 handles open per thread, running for almost 10 days now since last system reboot (mem usage looks normal too). |
| Stephen Brooks 2007-08-21 15:11:50 | I'm running 4 threads and the leaked handles appear to be opening in batches of 4, not every timestep, just some. They're not being cleared at the end of simulations. I'll see if I can find where they're coming from! |
| Hydrox 2007-08-22 09:31:49 | after somem runtime Muon piles up handles here too, they all are on Muonlattices. i think they get opened on every run start but are not closed. |
| Stephen Brooks 2007-08-23 10:26:31 | What do you mean by "Muonlattices"? Are they file handles? At the moment I can only see them in task manager, so it doesn't give me any more details. |
| Xanathorn 2007-08-23 14:58:50 | 6.500 Handles per thread now, running 2 threads. Indeed the handles don't close with a new simulation when I was watching task manager for a while, so slowly piling up. |
| Hydrox 2007-08-24 11:35:24 | The Handles are File handles in the lattices directory. |
| Stephen Brooks 2007-10-26 10:23:52 | Good news: I've found a few instances in my code where handles (usually for a file search within the lattices directory) weren't closed in some cases with the FindClose(h); call. Haven't yet tested to see if this fixes the bug, will update here when I do... |
