[Pharo-project] image freezes when setting time "back"
Hi I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation? Sorry if this message got sent twice. I had some trouble with the mailing list. Cheers Philippe
On Sat, Jul 16, 2011 at 8:07 PM, Philippe Marschall <kustos@gmx.net> wrote:
Hi
I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation?
Yes. It seems the known limitation of Cog VM that uses clock and something related to heartbeat and etc...When you change time you confuse Cog generating a freeze. At least I remember that something like that could happens. Try with a non-Cog VM. Sorry if this message got sent twice. I had some trouble with the
mailing list.
Cheers Philippe
-- Mariano http://marianopeck.wordpress.com
On Jul 16, 2011, at 8:07 PM, Philippe Marschall wrote:
Hi
I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation?
not that we are aware of. what a bug.... :) did you try with Squeak and did it behave the same? stef
Sorry if this message got sent twice. I had some trouble with the mailing list.
Cheers Philippe
On 16 July 2011 23:11, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Jul 16, 2011, at 8:07 PM, Philippe Marschall wrote:
Hi
I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation?
not that we are aware of. what a bug.... :)
i reported it and we discussed it months ago.
did you try with Squeak and did it behave the same? stef
Sorry if this message got sent twice. I had some trouble with the mailing list.
Cheers Philippe
-- Best regards, Igor Stasenko AKA sig.
On 16.07.2011 23:28, Igor Stasenko wrote:
On 16 July 2011 23:11, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Jul 16, 2011, at 8:07 PM, Philippe Marschall wrote:
Hi
I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation?
not that we are aware of. what a bug.... :)
i reported it and we discussed it months ago.
So I don't need to report a bug or anything? Cheers Philippe
Hi
I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation?
not that we are aware of. what a bug.... :)
i reported it and we discussed it months ago.
So I don't need to report a bug or anything?
probably on the cog issue tracker.
Cheers Philippe
On 17.07.2011 12:17, Stéphane Ducasse wrote:
Hi
I have had the following experience. I'm running Pharo 1.3 on a Linux box where the time is set on start up using ntp. The hardware clock is set to the local time (because I'm dual booting). When there is no network connection during booting the system the clock is two hours "ahead" until I get network connection and set the time using ntp. When a Pharo image is running during this the UI freezes and doesn't react anymore. Does anybody else observe this? Is this a known limitation?
not that we are aware of. what a bug.... :)
i reported it and we discussed it months ago.
So I don't need to report a bug or anything?
probably on the cog issue tracker.
Indeed: http://code.google.com/p/cog/issues/detail?id=15 Cheers Philippe
participants (4)
-
Igor Stasenko -
Mariano Martinez Peck -
Philippe Marschall -
Stéphane Ducasse