I'm using an html filter (ala junkbusters) called
Proxomitron (proxomitron.cjb.com) through wine. I find
that this program works great, except that it leaves a
trail of unkillable wine.bin jobs whenever it retrieves a
web page. Going to a page like slashdot results in ~8
wine.bin jobs that will never die, and can't be killed.
(I am using wine from CVS as of 3/12/02 or so)
Thinking that I'd be a good samaritan (and try to learn
something about debugging), I ran wine with --debugmsg
+relay, brought up slashdot, then terminated proxomitron.
Searching for CreateThread, I found 21 calls.
Searching for ExitThread, I found 20 calls.
But I was left with 8 unkillable wine.bin processes.
(While the program was running there were 10 wine.bin
processes, plus wineserver running)
At this point I didn't know what to try next. Any
pointers would be appreciated.
I have tried this with several Proxomitron releases
(going back about a year) with the same results. All this
leads me to think it isn't the application's fault, but
a wine issue (besides that it can run fine for months
at a time on my windows box, but causes me to reboot
once per week on my linux box).
I had tried previous wine builds, but a Jan 12 CVS build
wouldn't run it at all, and a mid November build wouldn't
allow it to connect to the internet.
Thanks,
.Geoff
-----------------------------------------------------
Protect yourself from spam, use http://sneakemail.com
