New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
print is not working in dart2js web workers #10224
Comments
Added this to the Later milestone. |
Added TriageForM5 label. |
Removed TriageForM5 label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
Can we revisit this issue please? console.log works in web workers. I checked Chrome and Firefox. Safari doesn't choke on it but neither does it print anything to the log (or maybe I don't know where to look for worker messages). Not sure about IE. Added C9 label. |
Just checked with IE11. console.log works just fine on the web worker. |
I just tried locally, and print goes to console.log for me. Do you have a repro? Added CannotReproduce label. |
Last time I checked was <1 month ago, and Dartium would throw if you tried to print from an isolate. Given the expectation that Dartium and dart2js behave the same I'd say this bug is not yet fixed. I'm ok if we want it to be a separate issue, but it is an issue and a big one for anyone trying to use isolates. |
Oh, if you do decide to create a separate issue, please assign C9 label to it. Thanks. |
This comment was originally written by matan...@google.com I tried this today, and Dartium still throws. It is possible that the dart2js version compiles OK, but that makes debugging your isolates and using Dartium hard without using zones and message passing ... for basic print(s). |
Added Triaged label. |
Calm down... A bug that has "dart2js" in the title and the description, talks about web workers (only used in dart2js), is assigned to Area-Dart2js and where you mention Firefox, Safari and IE is about dart2js. Given that this bug was that strongly marked as dart2js I didn't even test Dartium... #9: Yes. If you see a bug that is about dart2js and you see similar behavior in the VM or Dartium please file a new bug, or look if one already exists. I will mark it as c9 and ping the people that could fix them. Added AssumedStale label. |
I also opened 22163 for the issue of not printing from Dartium. Will link them. |
console.log doesn't work in web workers, consequently, print does not work.
It seems like Dartium has implemented print in non-DOM isolates by sending a message back to the root isolate. We should be able to do something similar in dart2js.
The text was updated successfully, but these errors were encountered: