Dartium bleeding edge exception #24494
Comments
|
We are interested, but can you try it again. There was a check-in this morning that fixes a number of polymer issues. |
|
Although maybe not right away, unless you're compiling it yourself. I don't think the bleeding edge version has even built yet for all platforms. |
|
Grat, I'll try it again, but I don't know yet when I'll have time, could be that's not before friday. |
|
I still get the same exception with Dartium from |
|
Update - my current exception looks a bit different:
Dart VM version: |
|
Current thinking is that we need a new Chrome roll of Dartium to resolve this. That roll is scheduled for 1.14 -- see #24218 -- so moving this to 1.14 also. |
|
This seems fixed after the last update (Dartium 1.13.0-edge.f3f358e5f38829f3284d7f922f2393d0803115dd) |
|
great! |
|
Since the bleeding edge update id did yesterday, it got it back:
Dartium:
|
|
I don't think that's the same as your original symptom. Do you have any more details about the circumstances? |
|
Right, it's not like the original, but the same or similar to the one mentioned in the comment #24494 (comment) The circumstances when I get the exception are the same though. I get this exception in every Polymer 1.0.0-rc application. |
|
I get the exception while the entry page (index.html) is loaded, after some delay, but before I do any user action. It looks like Polymer initialization is failing. |
|
/cc @jakemac53 |
|
If I revert to an older Dartium version
it works fine. |
|
The click_this example is working for me in that exact version, as well as in the tip of bleeding edge. I tried both building it myself on Linux and downloading the Mac version, and both were fine. |
|
I updated again to bleeding edge latest Dartium
VM:
The click_this example fails
After reverting Dartium to
the example works again. I have no idea what additional information I could provide to make this reproducible. |
|
Can you try putting a breakpoint on MutationObserver._create (line 27341 in html_dartium.dart in the current BE) and see what's happening in the wrap_jso call at the end. Presumably that's where you're getting a JsObjectImpl and not the corresponding Dart object. I'm suspicious there's something strange in your setup, because having all polymer initializations fail is something that we'd probably hear about pretty quickly. |
|
Dartium
without Dartium
Shows different code and this one works
|
|
OK, so the reason it's not getting wrapped is that the thing you're getting back is not [object MutationObserver], but looks like something wrapping a MutationObserver. The field _creationZone does not, as far as I can tell, exist anywhere in the Dart SDK or in Dartium. A quick google search shows something like that in Angular2. Is it possible you've got something from |
|
Nothing from Angular, just Polymer. Maybe @jakemac53 has any idea? |
|
I'm pretty sure it's the Polymer DevTools extension. That explicitly has code that monkey-patches system constructors to add that _creationZone field and replaces them with an unnamed function. Dartium relies on the constructor name when wrapping. |
|
You are right. |
|
Great. Filed #24776 and angular/zone.js#197 |
I had this issue with this Polymer 1.0.0-rc.2 example https://github.com/bwu-dart-playground/polymer1/tree/master/auto_binding_element
When I switched back to
Dart VM version: 1.13.0-edge.33b037125fbf5e8319a99fd5e5700441c921efde (Mon Sep 14 18:13:24 2015) on "linux_x64"the example was working fine.Are interested in such bug reports at this time?
The text was updated successfully, but these errors were encountered: