Is this a Memory Issue?
-
I am running into something of a problem when I open one too many documents with my application. The application no longer opens any dialogs such as the new or open dialog windows. I get a system ping whenever I try to open a document in VC++ if I am running under debug and windows explorer is almost completely locked. I can click folders but it quickly goes back to the folder selected therefore doing nothing. I think the CPU meter from the Windows Task Manager is peaked at 100% but I have no way of checking where in the code things seem to be hung up. The system ping sounds like an error window but there isn't an error window appearing. Anyone have any ideas? May I be outextending the memory? I have Database ADO connections open but I have programmed them to only have the focused window have connections to the database. The other windows will close the database connections until focused. Hopefully I have given enough info. Thanks!
-
I am running into something of a problem when I open one too many documents with my application. The application no longer opens any dialogs such as the new or open dialog windows. I get a system ping whenever I try to open a document in VC++ if I am running under debug and windows explorer is almost completely locked. I can click folders but it quickly goes back to the folder selected therefore doing nothing. I think the CPU meter from the Windows Task Manager is peaked at 100% but I have no way of checking where in the code things seem to be hung up. The system ping sounds like an error window but there isn't an error window appearing. Anyone have any ideas? May I be outextending the memory? I have Database ADO connections open but I have programmed them to only have the focused window have connections to the database. The other windows will close the database connections until focused. Hopefully I have given enough info. Thanks!
This looks more like resource exhaustion rather memory exhaustion; I’ve seen similar behaviour when applications create too many socket connections with dedicated threads serving such socket connections.
-
This looks more like resource exhaustion rather memory exhaustion; I’ve seen similar behaviour when applications create too many socket connections with dedicated threads serving such socket connections.
Can you elaborate a little? I'm slightly confused. Resource as in Dialogue resource? Database connection resource? There isn't any internet logic nor do I think I have coded thread logic. I'm just trying to figure out where I should be looking in my code for this issue. I stepped through and noticed that the OpenDocument method will parse through fine however when it returns from this method into whatever method called it, then it starts to act this way. Thanks!