-
Notifications
You must be signed in to change notification settings - Fork 10
pub serve hangs forever after a change (using the web-components transformer) #27
Comments
Re-opening this as we should try to fix the actual issue. The current fix creates a new resolver every time, which is probably going the have bad performance implications. |
@jakemac53 For me, the deadlock occurs in this method: If I don't run this method, the deadlock won't occur. If I run this method (and if don't do anything else after running this method), the deadlock occurs. If I change: var resolver = _resolvers.putIfAbsent(
id, () => new ResolverImpl(dartSdk, dartUriResolver, options: options)); to var resolver = new ResolverImpl(dartSdk, dartUriResolver, options: options)); then everything goes fine as well |
Thanks for investigating this, the actual problem is we were never releasing the resolver inside our web_components transformer :). You can see a mention of that in the comments for that method. I will work on a pull request and release a new version asap. |
published as 0.12.0+1 |
pub serve hangs forever after a change (using the web-components transformer)
similar to these issues:
dart-archive/angular.dart#1709
dart-archive/angular.dart#1276
The text was updated successfully, but these errors were encountered: