Re: [Pharo-dev] Interrupting process which hangs on recursion

2016-09-19 10:44 GMT+02:00 Tudor Girba : > Great work, Denis! > > We have to look at how the GTDebugger works with large stacks. Could you > please open an issue for that? > Done 19109

Re: [Pharo-dev] Interrupting process which hangs on recursion

Great work, Denis! We have to look at how the GTDebugger works with large stacks. Could you please open an issue for that? Cheers, Doru > On Sep 19, 2016, at 10:36 AM, Denis Kudriashov wrote: > > So I opened this case 19108 and submitted slice which restricts logging

Re: [Pharo-dev] Interrupting process which hangs on recursion

So I opened this case 19108 and submitted slice which restricts logging time to 100 milliseconds. (it should be enough, look at issue explanation). But also there is some problem with

Re: [Pharo-dev] Interrupting process which hangs on recursion

> On 16 Aug 2016, at 10:11, Denis Kudriashov wrote: > > > 2016-08-14 10:19 GMT+02:00 Sven Van Caekenberghe >: > But the slowness comes from printing a too large stack, no ? > Why not just limit the size of the stack being printed ? >

Re: [Pharo-dev] Interrupting process which hangs on recursion

2016-08-14 10:19 GMT+02:00 Sven Van Caekenberghe : > But the slowness comes from printing a too large stack, no ? > Why not just limit the size of the stack being printed ? > Maybe it is better to limit time which could be spend on log writing. Sometime I guess writing to log

Re: [Pharo-dev] Interrupting process which hangs on recursion

2016-08-16 9:50 GMT+02:00 Tudor Girba : > Hi, > > I was referring to the fact that when we press Cmd + . , the halt is being > logged in the PharoDebug.log, and this delays the debugger popping up, and > one proposal was to not log these direct user actions. > I would say,

Re: [Pharo-dev] Interrupting process which hangs on recursion

Hi, I was referring to the fact that when we press Cmd + . , the halt is being logged in the PharoDebug.log, and this delays the debugger popping up, and one proposal was to not log these direct user actions. Cheers, Doru > On Aug 16, 2016, at 9:41 AM, stepharo wrote: > >

Re: [Pharo-dev] Interrupting process which hangs on recursion

What is a user log? Stef Le 14/8/16 à 09:24, Tudor Girba a écrit : Hi, On Aug 14, 2016, at 9:14 AM, Max Leske wrote: Awesome Denis! On 13 Aug 2016, at 10:54, Tudor Girba wrote: Very cool analysis! What would your proposal be in this case?

Re: [Pharo-dev] Interrupting process which hangs on recursion

Thanks denis. So our discussions were good :) Le 13/8/16 à 10:42, Denis Kudriashov a écrit : We had discussion on reasons why cmd+. is not always working. I made simple test which shows that VM is not issue. Following code normally stops after 20 seconds: hanging := [1 seconds wait. 1

Re: [Pharo-dev] Interrupting process which hangs on recursion

+1 on not logging by default, but when using images as servers and/or running headless it seems that logging interrupts would be desirable. Sven, I think that Pharo already does some truncation of the stacks and frankly IMHO, if you are going to truncate the stack don't bother writing it at

Re: [Pharo-dev] Interrupting process which hangs on recursion

But the slowness comes from printing a too large stack, no ? Why not just limit the size of the stack being printed ? > On 14 Aug 2016, at 09:24, Tudor Girba wrote: > > Hi, > >> On Aug 14, 2016, at 9:14 AM, Max Leske wrote: >> >> Awesome Denis! >>

Re: [Pharo-dev] Interrupting process which hangs on recursion

Hi, > On Aug 14, 2016, at 9:14 AM, Max Leske wrote: > > Awesome Denis! > >> On 13 Aug 2016, at 10:54, Tudor Girba wrote: >> >> Very cool analysis! >> >> What would your proposal be in this case? > > Some ideas: > > - perform logging in a separate

Re: [Pharo-dev] Interrupting process which hangs on recursion

Awesome Denis! > On 13 Aug 2016, at 10:54, Tudor Girba wrote: > > Very cool analysis! > > What would your proposal be in this case? Some ideas: - perform logging in a separate process - only log user interrupt once for any given time interval, i.e., while a previous

Re: [Pharo-dev] Interrupting process which hangs on recursion

Very cool analysis! What would your proposal be in this case? Doru > On Aug 13, 2016, at 10:42 AM, Denis Kudriashov wrote: > > We had discussion on reasons why cmd+. is not always working. > I made simple test which shows that VM is not issue. Following code normally >

[Pharo-dev] Interrupting process which hangs on recursion

We had discussion on reasons why cmd+. is not always working. I made simple test which shows that VM is not issue. Following code normally stops after 20 seconds: hanging := [1 seconds wait. 1 recursionTest] newProcess. hanging priority: Processor activePriority + 10. interruptor := [ 20 seconds