Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Jul 1999 06:49:04 -0400 (EDT)
From:      Thomas David Rivers <rivers@dignus.com>
To:        glewis@ares.maths.adelaide.edu.au, jobaldwi@vt.edu
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Wine breakage...
Message-ID:  <199907211049.GAA01490@lakes.dignus.com>
In-Reply-To: <199907210901.SAA28277@ares.maths.adelaide.edu.au>

next in thread | previous in thread | raw e-mail | index | archive | help
> I'm trying to update the port for emulators/wine to the 990704 version, but I'm
> having some problems.  Basically, it builds fine, but when I try to run a
> program (for instance, freecell) it just sucks up memory until I run out of
> swap (which usually means X is killed, even though Wine is the one taking up
> all the swap space (guess the algorithm to find which process to kill doesn't
> take swap space into account)).  Here's the top lines from top (sorted by size):
> last pid: 38341;  load averages:  1.37,  1.40,  1.33   up 12+22:41:48  20:50:56
> 75 processes:  3 running, 70 sleeping, 1 stopped, 1 zombie
> CPU states: 97.3% user,  0.0% nice,  2.3% system,  0.4% interrupt,  0.0% idle
> Mem: 23M Active, 10M Inact, 22M Wired, 4500K Cache, 7447K Buf, 620K Free
> Swap: 152M Total, 123M Used, 29M Free, 81% Inuse, 44K In
> 
>   PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
> 38324 john      40   0   334M  2136K STOP     0:01  0.00%  0.00% wine
> 26342 root       2   0 29256K 17100K select  21:37  3.47%  3.47% XF86_SVGA
> 38322 john       2   0  6204K   328K select   0:00  0.00%  0.00% wine
> 
> Any suggestions?  The patches for the updated Wine port are available upon
> request.

 Actually - from this - to me, it looks like X is taking up all the space.

 This is likely some issue/bug/interaction between Wine and X11 causing
 the X server to have to allocate a lot of space, or do some other work.

 You could get really "low level" and trace the X11 events (using something
 like Xscope) to see what X11 request(s) could be causing the problem. 
 But, that is probably the "long way around."

 However, something is causing the X server to have difficulty...

	- Dave Rivers -


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907211049.GAA01490>