Austin has a workaround for the problem that makes ie6 exit immediately ( http://code.google.com/p/winezeug/issues/detail?id=78 ). While testing it on guimark, wine ~.wine/drive_c/Program\ Files/Internet\ Explorer/IEXPLORE.EXE http://www.craftymind.com/factory/guimark/GUIMark_HTML4.html I noticed something strange when I closed ie6 after running for a few seconds. Either I see some sort of file leak (and this is with a fully vanilla fresh wine): ... wine client error:10c: pipe: Too many open files fixme:wininet:InternetSetOptionW INTERNET_OPTION_COOKIES_3RD_PARTY; STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_REQUEST_PRIORITY (-1): STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CODEPAGE (65001): STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_ERROR_MASK(11): STUB wine client error:10d: pipe: Too many open files fixme:wininet:InternetSetOptionW INTERNET_OPTION_COOKIES_3RD_PARTY; STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_REQUEST_PRIORITY (-1): STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CODEPAGE (65001): STUB fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_ERROR_MASK(11): STUB ...
or I see Building font metrics. This may take some time... Font metrics: 0.0% done ... and the whole long font metric rebuilding process, which should never be happening anymore for local X servers (right?).
The "wine client error" comes from ntdll/server.c. It ought to be easy to get a backtrace from the problem using winedbg by setting a breakpoint, but I haven't managed to so far. Debugging this is complicated by the fact that GuiMark seems to crash my home router; maybe it does too many fetches too quickly.
Do other people see this, too?
Firefox seems to handle it well in wine, and doesn't show this problem. If this turns out to be an ie6 bug, we don't care, but there's some chance it's a wine bug. Guimark seems to be quite the stress test. - Dan