> If you see the gbx3 process memory becoming huge (in the KDE task
> manager for example), then the problem is in Gambas.
>
> If the problem is in the nvidia driver, you should see the xorg process
> becoming huge.
>
Yeah, logs shows that Xorg was closed due it hogging over 6 GB of memory.
Juss
Le 26/02/2012 22:49, Jussi Lahtinen a écrit :
> I reverted week back in revision, but I cannot reproduce the bug anymore.
> Maybe this has something to do with nvidia drivers, they don't seem to be
> very stable.
>
> Jussi
>
If you see the gbx3 process memory becoming huge (in the KDE task
manage
I reverted week back in revision, but I cannot reproduce the bug anymore.
Maybe this has something to do with nvidia drivers, they don't seem to be
very stable.
Jussi
On Sun, Feb 26, 2012 at 21:39, Jussi Lahtinen wrote:
> Qt4, but I think it happened also with GTK+.
>
> I tried to repeat the b
Qt4, but I think it happened also with GTK+.
I tried to repeat the bug with GTK+ to make sure, but when I removed the
workaround, nothing happened.
And now nothing happens also with Qt4!?!?
I don't know what has changed. System update... something with new Gambas
revision...? No idea.
Right now
Le 25/02/2012 23:06, Jussi Lahtinen a écrit :
> I can't manage to isolate the problem and I can't send the source.
>
> Right now I'm using following workaround;
>
> Draw.Begin(tmpPic)
> Draw.Image(imgKoko, 0, 0)
> Draw.Image(imgKarVe, 0, 0)
> Draw.Picture(picKohdistin, I.KarX - 12, I.KarY - 12)
> D
I can't manage to isolate the problem and I can't send the source.
Right now I'm using following workaround;
Draw.Begin(tmpPic)
Draw.Image(imgKoko, 0, 0)
Draw.Image(imgKarVe, 0, 0)
Draw.Picture(picKohdistin, I.KarX - 12, I.KarY - 12)
Draw.End()
Draw.Picture(tmpPic, 0, 0)
So, using temporary
Am 19.02.2012 23:15, schrieb Benoît Minisini:
> Le 19/02/2012 22:52, Jussi Lahtinen a écrit :
>> Unfortunately I can't send the project. But I keep on trying to isolate the
>> problem.
>> I'm pretty sure leak is from Gambas as it is fixed by commenting out the
>> three lines.
>>
>> Jussi
>>
>>
>
>
Le 19/02/2012 22:52, Jussi Lahtinen a écrit :
> Unfortunately I can't send the project. But I keep on trying to isolate the
> problem.
> I'm pretty sure leak is from Gambas as it is fixed by commenting out the
> three lines.
>
> Jussi
>
>
I can't do anything without seeing the source of your proje
Le 19/02/2012 23:04, M. Cs. a écrit :
> I have similar issue:
> I have a module and private subs in it. I'm using string arrays
> declared inside that SUB. The SUB is invoked when I scan some
> folders/files. The memory consumption rises during this scan by around
> 30 MB, which is quite normal, si
I have similar issue:
I have a module and private subs in it. I'm using string arrays
declared inside that SUB. The SUB is invoked when I scan some
folders/files. The memory consumption rises during this scan by around
30 MB, which is quite normal, since I'm feeding memory with huge
amount of data.
ld pictures
> and was a brain teaser.
> -Fernando
>
>
> -- Original Message ---
> From: Benoît Minisini
> To: mailing list for gambas users
> Sent: Sun, 19 Feb 2012 19:30:31 +0100
> Subject: Re: [Gambas-user] Memory problems with Gambas3
>
> > Le
Unfortunately I can't send the project. But I keep on trying to isolate the
problem.
I'm pretty sure leak is from Gambas as it is fixed by commenting out the
three lines.
Jussi
2012/2/19 Benoît Minisini
> Le 19/02/2012 19:12, Jussi Lahtinen a écrit :
> > Hi!
> > I was debugging huge project
Le 19/02/2012 22:08, nando a écrit :
> I had a similar huge problem with pictures.
> I found it to be this:
> When I made a new picture, even if using an existing control,
> the old picture still consumed the memory - it wasn't freed.
> I solved it by doing (recalling from memory so I may have synt
d the memory
then making the new picture.
It chewed up all the memory keeping the old pictures
and was a brain teaser.
-Fernando
-- Original Message ---
From: Benoît Minisini
To: mailing list for gambas users
Sent: Sun, 19 Feb 2012 19:30:31 +0100
Subject: Re: [Gambas-user] M
Le 19/02/2012 19:12, Jussi Lahtinen a écrit :
> Hi!
> I was debugging huge project to find out why it's execution is slowed down
> to unusable, when suddenly screen went blank and I was logged out.
> Reason found from logs: Killed process 1264 (Xorg) total-vm:6406864kB,
> anon-rss:2751124kB, file-r
Hi!
I was debugging huge project to find out why it's execution is slowed down
to unusable, when suddenly screen went blank and I was logged out.
Reason found from logs: Killed process 1264 (Xorg) total-vm:6406864kB,
anon-rss:2751124kB, file-rss:784kB
So I ran out of memory. This shouldn't happen,
16 matches
Mail list logo
