#8007: [app_server] fully unresponsive when resizing window of big textfile ----------------------------------+---------------------------- Reporter: ttcoder | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: Servers/app_server | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: All ----------------------------------+---------------------------- Comment (by anevilyak): Replying to [comment:20 axeld]: > Is priority inversion really so hard to circumvent, though? If we only put this functionality into mutex, it would just need to adjust the current lock holder's thread priority if a higher priority thread enters its wait queue, right? Correct me if I'm wrong, but I thought the issue isn't threads that're also waiting on the mutex (since those by definition aren't going to be scheduled), but rather, other high priority threads that actually are ready and being scheduled, thus preventing the lower priority thread that holds the mutex from doing its work and releasing it again? A simple strategy could indeed be to boost the priority of the mutex owner until they unlock it again, but then the question would be, how much do you boost it by? -- Ticket URL: <http://dev.haiku-os.org/ticket/8007#comment:21> Haiku <http://dev.haiku-os.org> Haiku - the operating system.