Issue 4097 in pharo: Adjust Finder's scan process to userBackgroundPriority

Status: New
Owner: ----

New issue 4097 by [hidden email]: Adjust Finder's scan process to  
userBackgroundPriority
http://code.google.com/p/pharo/issues/detail?id=4097

Pharo image: Pharo-core
Pharo core version: Pharo1.3a
Latest update: #13172
Virtual machine used: <Pharo4.1.1 on Win32>
Class browser used (if applicable): "SystemBrowser default"

I typed in a word, checked the box for regex, and set Finder on Source.  It  
completely locked up Pharo, while running the CPU at 100%.  Because the  
process has equal status with the desktop, the user can't reach the Process  
Browser to terminate it (if there's a way while it's running, I don't know  
it).

Similar issues occur with Monticello.  When it is accessing SqueakSource it  
sometimes gets very slow, and there's nothing to do but wait.

If you click around the screen while the system is locked up, all the  
clicks get processed after it's done, which usually makes an ugly mess of  
things.

See Smalltalk By Example, Chapter 16



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

Updates:
        Cc: [hidden email]

Comment #1 on issue 4097 by marianopeck: Adjust Finder's scan process to  
userBackgroundPriority
http://code.google.com/p/pharo/issues/detail?id=4097

(No comment was entered for this change.)


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

Updates:
        Status: Closed

Comment #2 on issue 4097 by [hidden email]: Adjust Finder's scan  
process to userBackgroundPriority
http://code.google.com/p/pharo/issues/detail?id=4097

With Pharo 2.0 now beta, time has come to review bug reports that have not  
seen any activity in 2012.
To keep the amount of issues managable, we close reports that have not  
drawn any attention for over one
year.

The reporter (and thus owner) of the issue should:

  -> check the issue in 2.0. Is it still relevant?
  -> If yes, just add a note to the report and we will be opened again.


As your issue has not seen any attention for over a year, please consider  
to give more information.
A good idea can be to send a mail to the mailinglist to get other people to  
help fixing the bug or implementing
an improvement.




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

Updates:
        Labels: MigratedToFogBugz

Comment #3 on issue 4097 by [hidden email]: Adjust Finder's scan  
process to userBackgroundPriority
http://code.google.com/p/pharo/issues/detail?id=4097#c3

Issue migrated to https://pharo.fogbugz.com/f/cases/4143

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

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