Rico <wineforum-user@xxxxxxxxxx> wrote on March 27th: > >loltsy wrote: >> Looking at the virtual size of the process it starts around 2600M where with a 64bit system it started around 3600M. After flying around all over the world and running some instances it seems to float around the 3G mark. Well short of the 4G crash that takes about 30 seconds to get to on 64bit. > > >I tried that, too, with this result: > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >l32 w32: 5793 ich 20 0 2598m 8556 6524 S 0.0 0.3 0:00.16 notepad >l32pae w32: 5760 ich 20 0 2598m 8564 6536 S 0.0 0.1 0:00.21 notepad >l64 w32: 4445 Ricola 20 0 3622m 9040 6544 S 0.0 0.1 0:00.13 notepad > >This table shows the output of top after "rm -rf ~/.wine && wine notepad" on linux 32Bit, 32Bit+pae, 64Bit. The main difference is the VIRT memory. Why is it ~1GB higher on 64Bit systems than on 32Bit systems? > The results are quite interesting. It is possible there is unoptimized code in Wine 64 bit. The question I have is this immediately after running the program or after a set time period, say ten minutes? If it is immediately, then my statement is basically correct and work needs to be done to optimize code for 64 bit. If it is after ten minutes, then there is a leak somewhere that is causing this and it should be investigated. James McKenzie
