I have just noticed something wrong when using one of my rg2 programs
with ruby-1.8.7. It happened with ruby-1.8.7-p0, ruby-1.8.7-p17 and
ruby-1.8.7-p22, with rg2 0.16.0.
When doing a few operations on my program, after a few seconds
seconds, ruby crashes with the message “[BUG] object allocation during
garbage collection phase”. It is reported each time on a different
line of my program, and seems unrelated to rg2 library calls (e.g. it
can happen on calling IO.readlines, Iconv::iconv or simple calls on
some of my objects).
Are your programs exhibiting a similar behaviour? I think it might be
related to rg2+ruby because I find it difficult that such a “nasty”
bug would be left in ruby if it would affect all programs. (I cannot
easily test with rg2 0.17.0-rc1 unfortunately)
–
Guillaume C. - http://zarb.org/~gc/
When doing a few operations on my program, after a few seconds
seconds, ruby crashes with the message “[BUG] object allocation during
garbage collection phase”. It is reported each time on a different
line of my program, and seems unrelated to rg2 library calls (e.g. it
can happen on calling IO.readlines, Iconv::iconv or simple calls on
some of my objects).
Yes, is happening to me too. For me, it usually happens when making a
operation in a pixmap.
André
–
A cura para o tédio é a curiosidade.
Não há cura para a curiosidade. (Dorothy Parker)
bug would be left in ruby if it would affect all programs. (I cannot
easily test with rg2 0.17.0-rc1 unfortunately)
Just tested; doesn’t happen when using 0.17.0-rc1.
–
Guillaume C. - Guillaume Cottenceau
Guillaume C. wrote:
bug would be left in ruby if it would affect all programs. (I cannot
easily test with rg2 0.17.0-rc1 unfortunately)
Just tested; doesn’t happen when using 0.17.0-rc1.
ruby-gnome2 0.16 won’t work with ruby 1.8.7. 0.17.0-rc1 should be fine,
although there are some patches added afterwards.
There will be a rc2 shortly.
Hi,
In [email protected]
“Re: [ruby-gnome2-devel-en] rg2 misbehaving with ruby 1.8.7?” on Sat,
21 Jun 2008 23:52:46 +0200,
“Guillaume C.” [email protected] wrote:
bug would be left in ruby if it would affect all programs. (I cannot
easily test with rg2 0.17.0-rc1 unfortunately)
Just tested; doesn’t happen when using 0.17.0-rc1.
Umm…
I’ve fixed it in trunk after rc1…
Thanks,
kou
On Mon, Jun 23, 2008 at 11:30 AM, Joachim G.
[email protected] wrote:
Guillaume C. wrote:
bug would be left in ruby if it would affect all programs. (I cannot
easily test with rg2 0.17.0-rc1 unfortunately)
Just tested; doesn’t happen when using 0.17.0-rc1.
ruby-gnome2 0.16 won’t work with ruby 1.8.7.
Ah. Didn’t know about it. Then we should quickly release a new
version, because not supporting current stable version of ruby is not
so good. Or are you willing to publish a ruby-1.8.7 patch to rg2 0.16
for the meantime? I mean, rushing 0.17.0 because of that might lead to
releasing with breaks.
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
ruby-gnome2-devel-en mailing list
[email protected]
ruby-gnome2-devel-en List Signup and Options
–
Guillaume C. - Guillaume Cottenceau
Guillaume C. wrote:
ruby-gnome2 0.16 won’t work with ruby 1.8.7.
Ah. Didn’t know about it. Then we should quickly release a new
version, because not supporting current stable version of ruby is not
so good. […] I mean, rushing 0.17.0 because of that might lead to
releasing with breaks.
I agree with you that rushing the new version out is not a good idea.
After I tested the latest patches for myself we’ll release 0.17-rc2
soon.
Getting some feedback will take about 2-3 weeks before we can decide to
bring out 0.17.0 final or a rc3 then.
Or are you willing to publish a ruby-1.8.7 patch to rg2 0.16
for the meantime?
Most probably not. So much time passed and there are tons of fixes made
since 0.16 release. I think it’s easier to fix some outstanding bugs in
0.17 (which Kou does eagerly) than fixing it on the old release.
Joachim