[haiku-bugs] Re: [Haiku] #8007: [app_server] fully unresponsive when resizing window of big textfile

  • From: "ttcoder" <trac@xxxxxxxxxxxx>
  • Date: Thu, 17 Nov 2011 19:33:34 -0000

#8007: [app_server] fully unresponsive when resizing window of big textfile
   Reporter:  ttcoder        |      Owner:  axeld
       Type:  bug            |     Status:  new
   Priority:  normal         |  Milestone:  R1
  Component:  System/Kernel  |    Version:  R1/Development
 Resolution:                 |   Keywords:
 Blocked By:                 |   Blocking:  7285, 7882, 8136
Has a Patch:  0              |   Platform:  All

Comment (by ttcoder):

 @bonefish To keep the ball rolling on this I'm willing to work on a
 wannabe patch.. It won't be the Real Thing of course since I don't know
 what I'm doing in kernel-land, but it could end up being better than
 nothing for making the actual patch happen by someone who does ;-)

 I've found [http://cgit.haiku-
 os.org/haiku/tree/headers/private/shared/locks.h private/shared/lock.h]
 and [http://cgit.haiku-os.org/haiku/tree/headers/private/kernel/lock.h
 private/kernel/lock.h] ; the latter seems to be the right one. And struct
 mutex_waiter is defined [http://cgit.haiku-
 os.org/haiku/tree/src/system/kernel/locks/lock.cpp here].

 I'll have to re-read this thread several more times, as I'm still not sure
 if the patch needs to modify thread.cpp too, or just lock.cpp ? I mean, in
 order to implement "priority boosting", the strategy which is non-trivial
 but has best potential to solve this ticket, by opposed to the "insert
 waiting threads in the queue according to their priority", which is easier
 to implement but not the best strategy. (did I get this right).

 Hmmm maybe I should wait until the Svn/Git transition is finished before
 posting the links supporting this discussion, source code is annoying to
 read on the temporary server...

Ticket URL: <http://dev.haiku-os.org/ticket/8007#comment:29>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: