Dear Visualworkers,
I just migrated my development environment to 7.4.1. and now I have a strange problem with Store: when connected my CPU goes to 100% and stays there until I disconnect. I'm using Linux. Has anyone similar problems? I tried to find some infinite loop with help of Process Monitor unsuccessfully. Which process should be debugged for Store connection? Thanks and best regards Janko -- Janko Mivsek Systems Architect EraNova d.o.o. Ljubljana, Slovenia www.eranova.si tel: +386 1 514 22 55 fax: +386 1 514 22 56 gsm: +386 31 674 565 |
Janko Mivšek wrote:
> I just migrated my development environment to 7.4.1. and now I have a > strange problem with Store: when connected my CPU goes to 100% and > stays there until I disconnect. I'm using Linux. Has anyone similar > problems? We are at least two with exactely the same problem. No solution yet. Have a look at the following thread on this list: "[BUG] Unix VW7.4.1 sometimes runs hot" Bye |
In reply to this post by Janko Mivšek
Janko Mivšek wrote:
> I tried to find some infinite loop with help of Process Monitor > unsuccessfully. Which process should be debugged for Store connection? My guess is to look around the network code for the Store/PostgreSQL connection. Look for a tight loop around a read/fill buffer which returns zero bytes read. Anyway, that's just a will guess. Good luck. |
In reply to this post by Damien Cassou-3-2
Dear VisualWorkers,
I'm wondering if that problem is already solved and some patch exists somewhere? It seams that problem is not only with Store but with any TCP/IP application. Many times my Swazoo (Aida/Web) server causes 100% CPU burnout and it must be restarted. Many times, but not always. Because of that 7.4.1 is practically useless for me until this problem is solved. Best regards Janko Damien Cassou wrote: > Janko Mivšek wrote: >> I just migrated my development environment to 7.4.1. and now I have a >> strange problem with Store: when connected my CPU goes to 100% and >> stays there until I disconnect. I'm using Linux. Has anyone similar >> problems? > > We are at least two with exactely the same problem. No solution yet. > Have a look at the following thread on this list: > "[BUG] Unix VW7.4.1 sometimes runs hot" > > > > Bye > -- Janko Mivšek Svetovalec za informatiko EraNova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565 |
Janko Mivšek wrote:
> Dear VisualWorkers, > > I'm wondering if that problem is already solved and some patch exists > somewhere? You should have a look at the thread named: "[BUG] Unix VW7.4.1 sometimes runs hot" in this list. Here are some quotes: " I've created AR#50994: "A remote Postgres connection makes the Linux VM run hot" for this issue. Thanks to all who reported the problem. " " Just a quick update on the progress. It seems that the bug was located and squashed, it will however require a new VM build. The conclusion is that it likely affects all Unix VMs, not just Linux. It's not clear to me yet if this will be deemed enough to trigger a release of an official bug fix VM at this point. It should make the 7.5 VMs at the latest though. " |
And in a different thread, re: setting environment variables in the Mac OS X Intel X11 VM.
On Thu, 27 Jul 2006, Robert Westergaard wrote: > > I'm sure we'll get around to releasing a newer set of engines at some > time in the near future. I believe new engines that fix this problem, along with the VM using all the CPU on socket connections (VW running hot) and another bug I can't recall right now, will be available sometime over the next two weeks. Please don't take that as a promise that they will be here in two weeks, simply take it as a notice that internally we're moving forward with releasing new engines soon. At 05:37 AM 8/14/2006, Damien Cassou wrote: >Janko Mivek wrote: >>Dear VisualWorkers, >> >>I'm wondering if that problem is already solved and some patch exists somewhere? > >You should have a look at the thread named: "[BUG] Unix VW7.4.1 sometimes runs hot" in this list. > > >Here are some quotes: > >" >I've created AR#50994: "A remote Postgres connection makes the Linux VM run hot" for this issue. Thanks to all who reported the problem. >" > > >" >Just a quick update on the progress. It seems that the bug was located and squashed, it will however require a new VM build. The conclusion is that it likely affects all Unix VMs, not just Linux. It's not clear to me yet if this will be deemed enough to trigger a release of an official bug fix VM at this point. It should make the 7.5 VMs at the latest though. >" -- Alan Knight [|], Cincom Smalltalk Development [hidden email] [hidden email] http://www.cincom.com/smalltalk "The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross |
Alan, thank you for a promising information. Best luck at solving that
problem! JAnko Alan Knight wrote: > And in a different thread, re: setting environment variables in the Mac OS X Intel X11 VM. > > On Thu, 27 Jul 2006, Robert Westergaard wrote: > >> I'm sure we'll get around to releasing a newer set of engines at some >> time in the near future. > > I believe new engines that fix this problem, along with the VM using all > the CPU on socket connections (VW running hot) and another bug I can't > recall right now, will be available sometime over the next two weeks. > > Please don't take that as a promise that they will be here in two weeks, > simply take it as a notice that internally we're moving forward with > releasing new engines soon. > > > At 05:37 AM 8/14/2006, Damien Cassou wrote: >> Janko Mivšek wrote: >>> Dear VisualWorkers, >>> >>> I'm wondering if that problem is already solved and some patch exists somewhere? >> You should have a look at the thread named: "[BUG] Unix VW7.4.1 sometimes runs hot" in this list. >> >> >> Here are some quotes: >> >> " >> I've created AR#50994: "A remote Postgres connection makes the Linux VM run hot" for this issue. Thanks to all who reported the problem. >> " >> >> >> " >> Just a quick update on the progress. It seems that the bug was located and squashed, it will however require a new VM build. The conclusion is that it likely affects all Unix VMs, not just Linux. It's not clear to me yet if this will be deemed enough to trigger a release of an official bug fix VM at this point. It should make the 7.5 VMs at the latest though. >> " > > -- > Alan Knight [|], Cincom Smalltalk Development > [hidden email] > [hidden email] > http://www.cincom.com/smalltalk > > "The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross > > |
Just a question: is this problem fixed now? Or is there a reliable
workaround? I couldn't find any further messages about this bug. Cheers, Lukas On 14 Aug 2006, at 13:44, Janko Mivšek wrote: > Alan, thank you for a promising information. Best luck at solving > that problem! > > JAnko > > Alan Knight wrote: >> And in a different thread, re: setting environment variables in >> the Mac OS X Intel X11 VM. >> On Thu, 27 Jul 2006, Robert Westergaard wrote: >>> I'm sure we'll get around to releasing a newer set of engines at >>> some >>> time in the near future. >> I believe new engines that fix this problem, along with the VM >> using all >> the CPU on socket connections (VW running hot) and another bug I >> can't >> recall right now, will be available sometime over the next two weeks. >> Please don't take that as a promise that they will be here in two >> weeks, >> simply take it as a notice that internally we're moving forward with >> releasing new engines soon. >> At 05:37 AM 8/14/2006, Damien Cassou wrote: >>> Janko Mivšek wrote: >>>> Dear VisualWorkers, >>>> >>>> I'm wondering if that problem is already solved and some patch >>>> exists somewhere? >>> You should have a look at the thread named: "[BUG] Unix VW7.4.1 >>> sometimes runs hot" in this list. >>> >>> >>> Here are some quotes: >>> >>> " >>> I've created AR#50994: "A remote Postgres connection makes the >>> Linux VM run hot" for this issue. Thanks to all who reported the >>> problem. >>> " >>> >>> >>> " >>> Just a quick update on the progress. It seems that the bug was >>> located and squashed, it will however require a new VM build. The >>> conclusion is that it likely affects all Unix VMs, not just >>> Linux. It's not clear to me yet if this will be deemed enough to >>> trigger a release of an official bug fix VM at this point. It >>> should make the 7.5 VMs at the latest though. >>> " >> -- >> Alan Knight [|], Cincom Smalltalk Development >> [hidden email] >> [hidden email] >> http://www.cincom.com/smalltalk >> "The Static Typing Philosophy: Make it fast. Make it right. Make >> it run." - Niall Ross > -- Lukas Renggli http://www.lukas-renggli.ch |
I have not confirmed it but the new VM patch apparently fixes this, see:
http://www.cincomsmalltalk.com/CincomSmalltalkWiki/VisualWorks+7.4c+engines -Charles On Wed, 27 Sep 2006 12:22:16 -0400, Lukas Renggli <[hidden email]> wrote: > Just a question: is this problem fixed now? Or is there a reliable > workaround? I couldn't find any further messages about this bug. > > Cheers, > Lukas > > On 14 Aug 2006, at 13:44, Janko Mivšek wrote: > >> Alan, thank you for a promising information. Best luck at solving that >> problem! >> >> JAnko >> >> Alan Knight wrote: >>> And in a different thread, re: setting environment variables in the >>> Mac OS X Intel X11 VM. >>> On Thu, 27 Jul 2006, Robert Westergaard wrote: >>>> I'm sure we'll get around to releasing a newer set of engines at some >>>> time in the near future. >>> I believe new engines that fix this problem, along with the VM using >>> all >>> the CPU on socket connections (VW running hot) and another bug I can't >>> recall right now, will be available sometime over the next two weeks. >>> Please don't take that as a promise that they will be here in two >>> weeks, >>> simply take it as a notice that internally we're moving forward with >>> releasing new engines soon. >>> At 05:37 AM 8/14/2006, Damien Cassou wrote: >>>> Janko Mivšek wrote: >>>>> Dear VisualWorkers, >>>>> >>>>> I'm wondering if that problem is already solved and some patch >>>>> exists somewhere? >>>> You should have a look at the thread named: "[BUG] Unix VW7.4.1 >>>> sometimes runs hot" in this list. >>>> >>>> >>>> Here are some quotes: >>>> >>>> " >>>> I've created AR#50994: "A remote Postgres connection makes the Linux >>>> VM run hot" for this issue. Thanks to all who reported the problem. >>>> " >>>> >>>> >>>> " >>>> Just a quick update on the progress. It seems that the bug was >>>> located and squashed, it will however require a new VM build. The >>>> conclusion is that it likely affects all Unix VMs, not just Linux. >>>> It's not clear to me yet if this will be deemed enough to trigger a >>>> release of an official bug fix VM at this point. It should make the >>>> 7.5 VMs at the latest though. >>>> " >>> -- >>> Alan Knight [|], Cincom Smalltalk Development >>> [hidden email] >>> [hidden email] >>> http://www.cincom.com/smalltalk >>> "The Static Typing Philosophy: Make it fast. Make it right. Make it >>> run." - Niall Ross >> > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
Charles A. Monteiro wrote:
> I have not confirmed it but the new VM patch apparently fixes this, see: > > http://www.cincomsmalltalk.com/CincomSmalltalkWiki/VisualWorks+7.4c+engines This problem is in the list of bugs fixed in the 7.4c engines, and since I switched to 7.4c I haven't seen the problem, which I was seeing multiple times a day previously. Regards, -Martin |
Free forum by Nabble | Edit this page |