the dart2js compiled version of my app sometimes throws on startup: NoSuchMethodError : method not found: 'Symbol("[]")' Receiver: Instance of 'UnknownJavaScriptObject' #15193
Comments
|
Added Area-Dart2JS, Triaged labels. |
|
Removed Area-Dart2JS label. |
|
We're investigating this same bug in another app. Currently I think the issue might be that Chrome is reusing a FileEntry object from the first run and returning it from restoreEntry(). The FileEntry object will have a cached JsObject associated with it, but because the JsObject is from a different JS context, it's not recognized as a Dart object. The change of behavior with how long you wait to restart the app would be explained by the apps background page being shutdown. |
|
This comment was originally written by ross.dart.lan...@gmail.com Thanks for investigating this Justin |
|
To add a bit more info, I did add some debugging code to the compiled JS, and same same JS object is being returned across sessions. So, the app has been closed, but the background page is still running. On the second run of the app, the same object from the first run is returned from the chrome.restoreEntry() call. We then see the UnknownJavaScriptObject issue. |
|
This comment was originally written by ross.dart.lan...@gmail.com I have applied the fix from Justin's CL 105893010 to my local SDK and it fixes this issue - do we have an ETA on landing the change? thanks, |
|
I'll get the fix in asap Set owner to @justinfagnani. |
DartBot
added
Type-Defect
area-core-library
kevmoo
added
P2
matanlurey
added
the
closed-obsolete
This issue was originally filed by ross.dart...@gmail.com
r30437
Windows 7x64
The dart2js compiled version of my application throws the following error sometimes on startup:
NoSuchMethodError : method not found: 'Symbol("[]")'
Receiver: Instance of 'UnknownJavaScriptObject'
Arguments: ["isFile"]
The call stack where this happens is for an interop call using
dart:jsto the Chrome API methodrestoreEntry(id)to restore a file entry. So I am not 100% sure where the bug lies, whether with dart2js, dart:js, or Chrome. However, the Dartium (vm) version of my application does not experience this issue, so I suspect dart2js is involved somehow.The strange thing is that this only seems to happen if I launch the application 'quickly' after closing a previous session. If I twiddle my thumbs for a minute or two and then relaunch, the issue goes away and the application launches without issue. Chrome apps have a notion of a 'background script' that is possibly coming into play here, as I think it hangs around for a short while after the application windows close, before it is suspended.
Please let me know if there are any other details I can provide here. Thanks to zones, I am able to catch this and not crash, but the user doesn't get to restore any of their previous session, so it is not a very good situation. I thought I was maybe going crazy until I stumbled upon these guys seeing the same issue here:
googlearchive/chromedeveditor#215 (comment)
thanks :)
The text was updated successfully, but these errors were encountered: