Re: Memory Issues

Cody Harris wrote:

>Sorry for the top reply, but, when I was reading about a thread with the same problem, I tried the persistant wineserver with debug level 2, but then killed it, now I'm trying to start it again, *BUT*:
>
>[email protected]:~$ wineserver -p -d2
>Server: support for __WALL in wait4 found
>sock_init: shutdown() causes EOF
>atexit destroy of semaphore
>atexit destroy of shared_memory
>[email protected]:~$
>  
>
Well you it probably crashed and in the process of crashing it will not 
delete the sockets used for inter process fd passing. If you delete them 
from the wineserver-<nameofmachine> directory you should be able to 
start the wineserver on its own.

>
>On Sun, 6 Jun 2004 12:57:18 -0300,
>Someone named Cody Harris <[email protected]> wrote:
>
>  
>
>>I recently tried WineX (Recent CVS) on 2 machines.
>>
>>Machine 1: 
>>-> AMD Athlon +2600 (2.13 GHz)
>>-> 512 MB DDR ram
>>-> Slackware 9.1 (with 2.4.22 kernel)
>>
>>Machine 2:
>>-> AMD (Name unknown) (1 GHz)
>>-> 256 SD Ram
>>-> Slackware 9.1 (with 2.4.22 kernel)
>>
>>Both use an exisiting Windows 98 SE partition setup with WineSetupTK
>>
>>The error is as follows:
>>[email protected]:/mnt/swap2/windows$ wine notepad.exe
>>wineserver: not enough memory for allocation of 4099 bytes
>>start=0x90001000 present=0x903ffbeb total=0x3fffb8
>>atexit destroy of semaphore
>>atexit destroy of shared_memory
>>[email protected]:/mnt/swap2/windows$ free -m
>>             total       used       free     shared    buffers     cached
>>Mem:           503        454         48          0         28        248
>>-/+ buffers/cache:        177        325
>>Swap:          199          0        199
>>[email protected]:/mnt/swap2/windows$
>>
>>So, what gives? Are you working on the memory system? I know this is not a trouble shooting mailing list, but maybe you weren't aware of this error.
>>    
>>
Well more than likely you're using a windows registry rather than just a 
small registry. This is known to cause problems with the shared memory 
wineserver as the registry has to actually fit into the whole 4MB of 
memory (which is the max that can presently be allocated). At some point 
soon we'll be fixing that issue probably by allocating the size of the 
registry + some fixed amount. In order to do that, however, we need to 
move to a different manner of allocated shared memory.

You should be able to compile so that the shared memory is not used - 
look about line 31 of server/main.c and change the value of 
shared_memory_server to 0. That should do the trick for the time being.

>>Thanks
>>-- 
>>+---------------------+----------------------------+
>>| Cody Harris         | NEWS:                      |
>>| Nova Scotia, Canada | VParse production resumed. |
>>+---------------------+----------------------------+
>>    
>>
>
>
>  
>
Ciao,
Peter