almost ready to release except for two bugs
Hi, So⦠subject says all. We need to fix this two: - https://pharo.fogbugz.com/f/cases/14606 <https://pharo.fogbugz.com/f/cases/14606> - the NOT REPORTED IN TRACKER MC BUG! (What are you thinking guys? Report, report, REPORT!⦠I failed the Jedi examen⦠without report the bug does not exist) and we are ready to go. Of course, we will try to fix between today and tomorrow⦠but even if we succeed, since âyou shall not go into production a fridayâ, release will be monday. cheers, Esteban
Esteban I got a kind of endless loop open a debugger.... but I cannot reproduce it :( Ask camille if he could reproduce the bug of the RB rename method. Stef Le 9/4/15 11:42, Esteban Lorenzano a écrit :
Hi,
So⦠subject says all. We need to fix this two:
- https://pharo.fogbugz.com/f/cases/14606 - the NOT REPORTED IN TRACKER MC BUG! (What are you thinking guys? Report, report, REPORT!⦠I failed the Jedi examen⦠without report the bug does not exist)
and we are ready to go.
Of course, we will try to fix between today and tomorrow⦠but even if we succeed, since âyou shall not go into production a fridayâ, release will be monday.
cheers, Esteban
Am 09.04.2015 um 15:43 schrieb stepharo <stepharo@free.fr>:
Esteban
I got a kind of endless loop open a debugger.... but I cannot reproduce it :( Ask camille if he could reproduce the bug of the RB rename method.
I experienced this a lot of times but I cannot reproduce either. I thought you can trigger it if you have one halt that opens the debugger and then proceed to the next code segment that contains a halt, too. But I'm not sure. I only know that sometimes I'm lucky after pressing cmd-. 50 times to open 50 debuggers but have an escape back into the UI thread. Most of the time it does not work. It just opens debugger windows but I do not get back control to do anything. Norbert
Stef
Le 9/4/15 11:42, Esteban Lorenzano a écrit :
Hi,
So⦠subject says all. We need to fix this two:
- https://pharo.fogbugz.com/f/cases/14606 <https://pharo.fogbugz.com/f/cases/14606> - the NOT REPORTED IN TRACKER MC BUG! (What are you thinking guys? Report, report, REPORT!⦠I failed the Jedi examen⦠without report the bug does not exist)
and we are ready to go.
Of course, we will try to fix between today and tomorrow⦠but even if we succeed, since âyou shall not go into production a fridayâ, release will be monday.
cheers, Esteban
On 09 Apr 2015, at 3:43 , stepharo <stepharo@free.fr> wrote:
Esteban
I got a kind of endless loop open a debugger.... but I cannot reproduce it :(
Could it be you were debugging something involving "large" collections? (Say, a 30MB ByteArray ) inspecting/debugging such objects is impossible with the new tools generates so much overhead you get stuck in GC thrashing hell before they even open... Cmd-Dot to interrupt won't make things better, since the debugger that opens has the same object as self, and would take as long to generate the inspector item. I know it's too late for 4.0, but it would be nice if someone with the proper GT skills would look at SequenceableCollection gtInspectorItemsIn: to see if it couldn't be made a bit more efficient, for instance avoiding the whole display: [ :aCollection | (1 to: self size) collect: [ :index | index -> (self at: index) ] ]; shenanigans. Cheers, Henry
Le 9/4/15 16:09, Henrik Johansen a écrit :
On 09 Apr 2015, at 3:43 , stepharo <stepharo@free.fr> wrote:
Esteban
I got a kind of endless loop open a debugger.... but I cannot reproduce it :( Could it be you were debugging something involving "large" collections? (Say, a 30MB ByteArray ) inspecting/debugging such objects is impossible with the new tools generates so much overhead you get stuck in GC thrashing hell before they even open...
May be I was playing indeed with changes file.
Cmd-Dot to interrupt won't make things better, since the debugger that opens has the same object as self, and would take as long to generate the inspector item.
I know it's too late for 4.0, but it would be nice if someone with the proper GT skills would look at SequenceableCollection gtInspectorItemsIn: to see if it couldn't be made a bit more efficient, for instance avoiding the whole display: [ :aCollection | (1 to: self size) collect: [ :index | index -> (self at: index) ] ]; shenanigans.
Cheers, Henry
participants (4)
-
Esteban Lorenzano -
Henrik Johansen -
Norbert Hartl -
stepharo