New issue
Advanced search Search tips

Issue 918863 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Tab crash (AccessTokenFetched error: Invalid credentials)

Reported by gez...@gmail.com, Jan 3

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce the problem:
Local codebase, if desired I can upload a HTML page that can reliably reproduce this on my machine.

What is the expected behavior?

What went wrong?
I have a contenteditable element that is used as compose area for a chat application. The user can enter emoji and text.

When entering an emoji, followed by typing a letter, the tab reliably and immediately crashes. See attached crashlog.

I found the following three errors in the log, not sure which one is most relevant:

- [15189:15189:0103/165455.742372:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)
- [15189:15189:0103/165455.808554:ERROR:account_tracker.cc(240)] AccessTokenFetched error: Invalid credentials (1).
- [15189:15189:0103/165501.702137:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()

The same happens on CircleCI: https://circleci.com/gh/threema-ch/threema-web/3314

Not sure if one of those two issues is related:

- https://bugs.chromium.org/p/chromium/issues/detail?id=892351
- https://bugs.chromium.org/p/chromium/issues/detail?id=891277

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes 

Chrome version: Version 71.0.3578.98 (Official Build) Arch Linux (64-bit)  Channel: stable
OS Version: Arch Linux
Flash Version: 

Fresh browser profile, no login, no plugins.
 
chromium_log.txt
7.7 KB View Download
This is a TypeScript codebase. We're using Babel to transpile the codebase to an older ES version.

Previously we targeted Chrome 45. With that configuration, the crash does not occur. But when I change the target to Chrome 46, the crash occurs.

In the error trace, I see the function "getWord" being called. I generated the code using Chrome 45 and 46 as target and compared the two functions. Apart from the fact that 46 supports classes and 45 doesn't, the only difference in the body was this:

11,12c11
<         var chars = _toConsumableArray(input);
<
---
>         var chars = [...input];
52d50

Maybe the crash is related to the spread operator in a weird way?

I attached the two functions.
getword.45.js
1.3 KB View Download
getword.46.js
1.2 KB View Download
Indeed, if I take the generated source code (which crashes), and replace this

    const chars = [...input];

with this

    const chars = input.split('');

...then the crash does not occur.
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
gezuru@ Could you please provide latest 16 digit crash id from chrome://crashes for further triage.
Crash.png
37.4 KB View Download
kkaluri: I'm using Chromium, which does not contain crash reporting. If there's anything else besides the crashlog attached to the report that I can collect, let me know!
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 7

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: jbanavatu@chromium.org
Labels: Needs-Feedback
@gezuru: Could you please provide sample file for triaging this from our end. Also please provide screen-cast on reproducing this issue which would help in further triaging .

Thanks!

Sign in to add a comment