Am Dienstag 03 Oktober 2006 11:36 schrieb Alexandre Julliard:
> Robert Shearman <[EMAIL PROTECTED]> writes:
> > Nick Burns wrote:
> >> Does Linux have the same mem problem? -- does top show like 4GB of
> >> VSIZE on app start?
> >
> > The numbers seem bogus since 32-bit apps can only take up 4Gb of
On 3 oct. 06, at 08:09, Ken Thomases wrote:
The other really big chunk of VM (after Wine) is labeled as "STACK
GUARD". I believe the intent of STACK GUARD space is to generate
exceptions (EXC_BAD_ACCESS / SIGSEGV) if a stack grows beyond its
pre-allocated bounds. It's another 1.5GB! Thi
Robert Shearman <[EMAIL PROTECTED]> writes:
> Nick Burns wrote:
>> Does Linux have the same mem problem? -- does top show like 4GB of
>> VSIZE on app start?
>
> The numbers seem bogus since 32-bit apps can only take up 4Gb of
> VM. Wine does reserve 1.5Gb of VM on startup to ensure no system
> lib
On Oct 2, 2006, at 12:49 PM, Robert Shearman wrote:
Nick Burns wrote:
All the following have this VM ~=4GB on startup -- its not a
leaking problem... (afaict)
OGL/D3D -- WinRAR, GTAVC, Tribes2, (FlatOutDemo -- even thou it
dies on startup now -- still gets to ~4GB), SHOGO
NON-GL -- cmd (
Nick Burns wrote:
All the following have this VM ~=4GB on startup -- its not a leaking
problem... (afaict)
OGL/D3D -- WinRAR, GTAVC, Tribes2, (FlatOutDemo -- even thou it dies
on startup now -- still gets to ~4GB), SHOGO
NON-GL -- cmd (not even using X11), winecfg, StreamDown, MS VC++ 6,
MS
?
- Nick
From: Stefan Dösinger <[EMAIL PROTECTED]>
To: wine-devel@winehq.org
Subject: Re: Mem usage in Mac OSX
Date: Mon, 2 Oct 2006 12:43:30 +0200
Am Sonntag 01 Oktober 2006 13:30 schrieb Nick Burns:
> Im seeing some very odd behaviour in Mac OSX using wine -- and wondered
if
>
Am Sonntag 01 Oktober 2006 13:30 schrieb Nick Burns:
> Im seeing some very odd behaviour in Mac OSX using wine -- and wondered if
> anyone could enlighten me
>
> When I run any application -- I see it start with ~4GB of VM then
> depending on the app -- it goes upwards of 5.7GB in VM usage (>4GB?)
Im seeing some very odd behaviour in Mac OSX using wine -- and wondered if
anyone could enlighten me
When I run any application -- I see it start with ~4GB of VM then depending
on the app -- it goes upwards of 5.7GB in VM usage (>4GB?) in Activity
Monitor (usually because of texture loading o
