New issue
Advanced search Search tips

Issue 714807 link

Starred by 1 user
Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Sync calls via ThreadSafeInterfacePtr unnecessarily block the InterfacePtr thread

Project Member Reported by w...@chromium.org, Apr 24 2017 
ThreadSafeInterfacePtr supports sync calls but both the calling thread and the thread that the underlying InterfacePtr is bound to are blocked. 

However, the InterfacePtr thread doesn't need to block, and this is an annoying restriction because it means the InterfacePtr can't be bound to a thread that disallows blocking, like the IO thread.
Project Member

Comment 1 by sheriffbot@chromium.org, Apr 25 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by rockot@google.com, Nov 15

Cc: -w...@chromium.org -yzshen@chromium.org
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
Still valid, but pretty low priority since TSIP is used in exactly one place (WidgetInputHandlerManager).

TSIP is already a bit more complex than it should be, due to it emulating IPC::SyncMessageFilter::Send behavior for legacy reasons. When we can get rid of that behavior, it should be easier to also get rid of the blocking stuff.
►

Sign in to add a comment