Issue 5013 in pharo: World intermittently becoming a mess

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug

New issue 5013 by [hidden email]: World intermittently becoming a  
mess
http://code.google.com/p/pharo/issues/detail?id=5013

Pharo1.3 Latest update: #13320

Every once in a while, in my 1.3-rc image, the world becomes a mess.  
Specifically:
* moving windows without the fast dragging setting enabled leaves a trail
* previews from hovering over the task bar remain in the world and don't  
delete themselves when the mouse is no longer over the task bar

I haven't been able to reproduce it, but it's happened a few times. Has  
anyone else experienced this?

Attachments:
        Screen Shot 2011-11-23 at 1.01.31 PM.png  85.5 KB


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

Issue 5011 has been merged into this issue.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

This looks very much like something I have seen, not often but every couple  
of weeks maybe.

I can't say much about the cause.

It feels like it is related to debugging/breakpoints/unit testing, but then  
again, that is what you do all the time as a Smalltalk programmer.

I used to mark these images as broken, but I recently found out you can fix  
them: check your processes, Tools>Process Brwoser, there will be some bogus  
ones there (compare the list to a clean image), Terminate these and you  
will probably be good. There is a bogus UI process that is harder to  
terminate: inspect it and do a self terminate. You have to be a bit careful  
of course. I always do a Windows>Close all debuggers and a System>Restore  
display as well, but I not sure it helps.

HTH,

Sven


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 5013 by [hidden email]: World intermittently becoming  
a mess
http://code.google.com/p/pharo/issues/detail?id=5013

If that's the case, opening a debugger on the UI thread itself should start  
a new UI thread, so it might be worth looking into under which  
circumstances termination of the suspended while debugging one does not  
terminate correctly when you quit the debugger.
IIRC, the logic for what to do with the suspended process differs depending  
on how you quit the debugger. (Proceed, quit using window controls, etc.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

Yes, my problem too was with an extra UI process. Terminating it restored  
my image, but where did it come from?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: closed

Comment #5 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

for now I will close this entry as soon as we get a way to reproduce it we  
will open a new one and fix it.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Accepted

Comment #6 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

 From  
http://forum.world.st/Bug-reports-1-of-6-Damaged-Window-rectangles-on-Screen-td4256330.html :

1. Damaged Window rectangle painting all over.. as you drag the window over  
the World..

* This is just the repeatable test, but occurs very annoyingly with an  
image if we have debugged through some piece of Morphic UI code..
Infact this damaged rectangles/ lost refresh of World occurs very  
frequently with ordinary non forked UI stuff also. of other variants viz:  
SystemWindow etc..

* Transcript if used on / or STranscript.. the World repaint many a times  
starts popping up its TextMorph through other top windows.. while it sends  
the transcript text to it.


        [ | dialog builder |
        builder := UITheme exampleBuilder.
        dialog := builder newPluggableDialogWindow: 'BasicTestDamagedWindows'.
        dialog
                contentMorph: (dialog newRow: {dialog newColumn: {dialog newColumn:  
{dialog
                                                        newTextEntryFor: (ValueHolder new contents: 'text')
                                                        getText: #contents
                                                        setText: #contents:
                                                        help: 'hostName'}}});
                 model: self.
        World openModal: dialog ] fork.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #7 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

When I run the code snippet I do not have any problem on my mac with 1.3  
and 1.4.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #8 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

I just experienced this in a fresh 2.0 image (recent Cocoa Cog Jit VM; OS X  
10.7.3) after working for a few hours. There was that same extra UI  
process. I wasn't doing anything out of the ordinary, just fixing  
Chronology, running tests...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #9 on issue 5013 by [hidden email]: World intermittently  
becoming a mess
http://code.google.com/p/pharo/issues/detail?id=5013

Did you see it again?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker