Webogram: Error: Constructor not found

Created on 8 Nov 2017 · 11Comments · Source: zhukov/webogram

app.js:13 Error: Constructor not found: 3504867164 328784060 1992907048
    at TLDeserialization.fetchObject (app.js:57)
    at app.js:58
    at o (app.js:14)
    at app.js:14
    at m.$eval (app.js:14)
    at m.$digest (app.js:14)
    at m.$apply (app.js:14)
    at l (app.js:13)
    at b (app.js:13)
    at XMLHttpRequest.M.onload (app.js:13)

Can't login at all. Just freezing at Generating keys....

Source

irudoy

👍1

Most helpful comment

I can confirm it's some really weird bug in chrome, I'd call it "Schrodinger's typed array" lol
I'm investigating it to make a proper bugreport :|)

stek29 on 16 Nov 2017

😄3

All 11 comments

Are you using https://web.telegram.org?
This is really weird, since constructor 3504867164 (aka d0e8075c) was never used by tg.
So it's likely read something wrong right before that.
I'm unable to reproduce it.
If it still happens, please set a breakpoint on that throw, and look at local variables. One of them would contain full "path" to field currently being read.

stek29 on 8 Nov 2017

Yes, I'm using web.telegram.org

deserializer.fetchObject("Server_DH_Params", "RESPONSE");
...
var constructor = this.readInt(field ("RESPONSE") + '[id]');
constructor === 3504867164

irudoy on 9 Nov 2017

I am having this issue for a couple of days as well, but only on current Chrome Canary (64.0.3262.0 at the time of writing) on Mac OS. I'm having no problems on Chrome 61.

I had telegram tab open for pretty much forever and suddenly it just stopped working - it rendered a blank template with no chats/messages. Reload did not help and I tried clearing application data (cookies, local storage, dbs, etc...) which brought me to login page and now I'm experiencing exactly the same problem as described.

Here's the console output right after page load (note that numbers are different from @irudoy's, mine are: 3504867164 1309788097 3259107725)

l1bbcsg on 9 Nov 2017

If it still happens, please set a breakpoint on that throw, and look at local variables. One of them would contain full "path" to field currently being read.

@stek29 The code is minimized, it's not exactly clear which one is the path you're looking for. This is what local variables look like when this exception is thrown:

l1bbcsg on 9 Nov 2017

My Chrome version is 64.0.3260.2 dev (macOS 10.13.1).
I understand that this is unstable build, but I believe that we need to understand the cause of the problem before the stable channel is updated to 64.

irudoy on 9 Nov 2017

I also got this in google chrome canary(64.0.3262.0 Mac), but in my chrome(62.0.3202.89 ), it's OK, maybe this is an issue due to chrome canary?

ZxBing0066 on 10 Nov 2017

I also see this on several machines running Chrome dev 64.0.3260.2 on Linux. Maybe worth testing against latest chromium and reporting it as a regression if that's the only browser that doesn't work.