Hi all,
After the last round of gc updates, kaffe has been acting much better
with the app I'm writing (yay!)- it doesn't usually crash until after
two or maybe three days (before it seemed to be on a 8-16 hour schedule).
The crashes are all the same - around when it reaches its memory limit
(64M
Sure looks and sounds like a memory leak to me...
- Original Message -
From: "jrandom" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 21, 2003 10:31 AM
Subject: [kaffe] bug report: core dump after eating cpu (gc related?)
> Hi all,
>
> After the last round of gc upd
Hi!
I don't know if this is a blocker, but I'm unable to compile Kaffe - both 1.1.2 and cvs, on the new Fedora Core distribution.
There are some differences, but when compiling cvs it breaks in the make process with this message:
/bin/sh ./rebuildLib @essential.files
Compiling classes from @essen
Oh, its certainly a memory leak, I said the *application* isn't leaking
ram, as when I spent a few days w/ JProfiler profiling its memory and
CPU usage on a completely different OS and JVM (xp, sun 1.4.2), it used
a steady 2-3Mb (in addition to ~8-12 from the jvm), as opposed to on
freebsd/kaffe wh
Hi Ito,
Ito Kazumitsu wrote:
Hi,
The following patch solved this problem although it
reduced performance.
thanks for taking the time to find a fix. Could you check in an updated
kjc into kaffe's CVS and the patch into kaffe-extra?
cheers,
dalibor topic
__
Hi Jim,
Jim Pick wrote:
Hi,
It's getting to close to that time again. Isn't having a regular
release schedule fun?
Yep. I'd actually propose a faster release schedule: once a month after
1.1.3. There is so much changing every two months, that the steps
between releases are quite huge, so that
PatchSet 18
Date: 2003/11/21 22:56:39
Author: kaz
Branch: HEAD
Tag: (none)
Log:
Added kaffe-extras/patches/kjc-main-checkInitializers.diff.
This is to prevent some constant fields from being left unset.
Members:
patches/kjc-main-checkInitializers.diff:INITIAL->1.1
Hi Dalibor,
> ":" == Dalibor Topic <[EMAIL PROTECTED]> writes:
:> thanks for taking the time to find a fix. Could you check in an updated
:> kjc into kaffe's CVS and the patch into kaffe-extra?
I added the patch to kaffe-extras.
But I am having trouble with making kjc.jar because I do not
> I'm not so optimistic about a stable release that soon, as I don't think
> we should really cut that one based on time passed alone, but also
> define a list of features we want to see in, as well as platforms we
> want to see run, applications we want to offically list as supported in
> 1.2
Hi,
Since I am not a GregorianCalendar expert I was hoping that someone
could review the following patch which I have in my tree from Ito
Kazumitsu. He and I wrote a couple of mauve test cases which are fixed
by this and I see no new failures. But people didn't seem to be
completely comfortable wi
PatchSet 19
Date: 2003/11/22 05:52:16
Author: guilhem
Branch: HEAD
Tag: (none)
Log:
Updated build.xml to use Ito's patch.
Members:
build.xml:1.10->1.11
Index: kaffe-extras/build.xml
diff -u kaffe-extras/build.xml:1.10 kaffe-extras/build.xml:1.11
--- kaffe-extras/build.xml:1.10 Tue Oct
Ito Kazumitsu wrote:
Hi Dalibor,
":" == Dalibor Topic <[EMAIL PROTECTED]> writes:
:> thanks for taking the time to find a fix. Could you check in an updated
:> kjc into kaffe's CVS and the patch into kaffe-extra?
I added the patch to kaffe-extras.
But I am having trouble with m
PatchSet 4166
Date: 2003/11/22 05:57:28
Author: guilhem
Branch: HEAD
Tag: (none)
Log:
Included Ito's patch.
Members:
ChangeLog:1.1758->1.1759
libraries/javalib/kjc.jar:1.24->1.25
Index: kaffe/ChangeLog
diff -u kaffe/ChangeLog:1.1758 kaffe/ChangeLog:1.1759
--- kaffe/ChangeLog:
13 matches
Mail list logo