Issue metadata
Sign in to add a comment
|
web.flock.com app crashes on signup/login
Reported by
officeta...@gmail.com,
Mar 12 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.146 Safari/537.36 Steps to reproduce the problem: 1. go to https://web.flock.com and sign up with a new (gmail.com) email id 2. after completing sign up steps (around 5 screens) .. when it lands into the app, we see an Aw snap 3. reloading the page also shows the same Aw snap (but not consistently) What is the expected behavior? It shouldnt crash What went wrong? when tried on Chrome with --enable-logging, it shows this error: [21291:775:0312/153208.920196:ERROR:bad_message.cc(25)] Terminating renderer for bad IPC message, reason 188 Crashed report ID: yes How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? Yes Chrome 64 Chrome version: 65.0.3325.146 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Uploaded Crash Report ID 6f4930326c58d346 (Local Crash ID: b02973f9-c56c-49f1-b7f5-fd4821e27686) We used chromium bisect-builds util to get to this message: You are probably looking for a change made after 522194 (known good), but no later than 522207 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/e9ef5260cdea70b3f1aabf1bf19ee1985d01c236..8e333b2c009f030f93165d00c7a858d6bb1518a2
,
Mar 12 2018
As per our bisecting, the following change is most probable cause of the crash -- https://chromium.googlesource.com/chromium/src/+/0c8d550bb4f71ad5fb82abbcf772abb9ff42e25c
,
Mar 12 2018
Looks like another issue reported with same problem - https://bugs.chromium.org/p/chromium/issues/detail?id=821022 So either of the issue can be closed as Duplicate
,
Mar 12 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by at...@flock.com
, Mar 12 2018