MKairys wrote:[...]
I don't think so, JRz. The pages of memory that were used are marked available in the page tables but there is no actual "disposal" that would take any time. [...]
You're right of course. My choice of words was not the most appropriate one...
[The following goes for the Pro version only by the way. It has to do with searches and scraps; so a bit off topic I guess]
What I meant to say is that I observed sluggishness when using extensive searching, which takes a lot of memory if you have many (a great many I might add) found items in your search results. This can lead to extensive disk thrashing, since (physical) memory is limited and Windows starts to swap to get its hands on more memory space in the form of the page file.
I observed that when the search results are discarded, it takes a long time for the process to regain its original memory footprint. This can take minutes. In this time X² is cleaning up the structures it created to accomodate for the (large amount of) search results.
Probably doesn't have to anything to do with the problem at hand, but I threw it in anyway, so we don't leave any stone unturned
I've seen three "Ftp" process hanging there in Win98 long after x2 was shut down.
Not 100% sure if it was x2, but AFAIR it's only x2 that I was playing with (ftp) that evening (wrong credentials, etc). I'll try to reproduce.
ok, I reproduced the problem. The process with no windows contains 6 threads. What's interesting is: if I open a single window, the process contains 8 threads, just like if I open two windows when this isn't happening. Hmm... highly suspect.
It wouldn't surprise me that at least one cause is from ftp difficulties.
As Far As IRecall - a couple of days ago, I had had ftp connection probs in prior v, of x2 immediately before I closed it & tried to install the latest version & then discovered that it was still the old one (because of unclosed process).
[maybe you can blame it on the crude IE interface for ftp-with-IE? ]
I sort of just realised it was doing this when xplorer2 started up a lot quicker than it should. Can't say there was any specific pattern of events. I tried reproducing the problem through events that I thought might be the cause but it was fruitless. Will post if I find something new though.
nikos,
I (finally) have come upon a reproducible case where x2 process stays open after closing all windows.
It happens every time, if I have viewed a media file in QuickView pane, where x2 calls WMP.
[edit:]I got a dbmon spew as described in PM I sent.
PS - following is the "tail" of that dbmon output, likely when problem was triggered:
...
...
4072: >>>>> TREE: expanding node...
4072: *** TID=ac4, Generating folder instance '::{20D04FE0-3AEA-1069-A2D8-08002B30309D}\C:\Documents and Settings\Dan'
4072: Filesystem path = C:\Documents and Settings\Dan
4072: Shell attributes: (0x7080017f) FILESYSANCESTOR | FILESYSTEM | STORAGEANCESTOR |
4072: DESCRIPTIONID: 3(FS_DIRECTORY) : {00000000-0000-0000-0000-000000000000}
4072: Assigned folder type: FITYPE_NORMAL [forced]
4072: Folder CLSID: {F3364BA0-65B9-11CE-A9BA-00AA004AE837}
4072: Enumerated 16 objects in the folder, code=1
4072: <<<<< TREE: node expanded (ok)
*********** At this point, noted 8 threads in kenny process
*********** selected a .mpg file, winMediaPlayer then shows blank "screen in QV pane, still 8 threads in process
*********** Next L-Click on playarrow in QView pane; threads=11, then 12 & video plays in QV pane
*********** threads go as high as 13 and back to 11 when video finishes, then get following dbmon output:
4072: @@@ thread_ac4 unexpected WM_NULL for 0
4072: Thread ac4 pump: unrecognized message 0 ignored
4072: @@@ thread_ac4 unexpected WM_NULL for 0
4072: Thread ac4 pump: unrecognized message 0 ignored
*********** Now I close x2, * get following dbmon output:
4072: ThreadID=ac4: Destroying frame 0x002001ae 'ATL:ExplorerFrame' [xplorer? - Dan's Documents @ C:\...]
*********** At this point x2 application is closed (no open windows) but threads=8
ABOVE IS VERY REPEATABLE
WMP 9.000.00.3075 ON XP-PRO, SP1
{x2 debug version 1.0.0.2 executable dated 7/4/04}
[/edit] ____________________________________________________________________________________________
If I close the preview pane; then quit x2, the process stays open, but nthreads drops to 7.
PS: I cannot duplicate the problem on w98 with wmp 6.4 ... nor with wmp 7.01 on another w98 machine, so problem must be interfacing with a new "feature" in wmp 8 or 9
Last edited by fgagnon on 2004 Jul 18, 18:56, edited 1 time in total.
this isn't going to be easy to fix either
wmp9 somehow hijacks x2's message pump (the heart of the program) to do some useless visual effects -- or whatever else it's trying to do -- and as a result messages get lost, including the all important quit message; it never reaches the intended recipient and x2 hangs
god damn you balmer!
(i bet it's all his fault since he is the stingy clown behind money cutting exercises at m$; pay peanuts get monkeys for programmers )
]
)
)