New issue
Advanced search Search tips

Issue 617596 link

Starred by 2 users
Status: Duplicate
Merged: issue 618381
Owner: ----
Closed: Jun 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Problem with the WebSql Database

Reported by epsilonn...@gmail.com, Jun 6 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36

Steps to reproduce the problem:
1. Execute a transaction (websql) usually using an insert or update statement
2. The sql statement finishes correctly but after it finishes the tab crashes
3. 

What is the expected behavior?

What went wrong?
The tab crashed. All i can see is aw snap page.

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? No 

Did this work before? Yes It worked up until chrome version 50

Chrome version: 51.0.2704.79  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 21.0 r0

Comment 1 by kavvaru@chromium.org, Jun 7 2016

Labels: Needs-Feedback
 epsilonnet7@ Thanks for the issue.

Could you please provide us the crash id from chrome://crashes to triage the issue further.

Thanks,

Comment 2 by epsilonn...@gmail.com, Jun 7 2016 

Hello ,
I don't see  a crash id. My crash log in chrome://crashes is empty.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 8 2016

Labels: -Needs-Feedback Needs-Review
Owner: kavvaru@chromium.org
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by kavvaru@chromium.org, Jun 14 2016

Labels: -Needs-Review Te-NeedsFurtherTriage
Owner: ----

Comment 5 by cbiesin...@chromium.org, Jun 23 2016

Components: Blink>Storage>WebSQL

Comment 6 by michaeln@chromium.org, Jun 29 2016

Mergedinto: 618381
Status: Duplicate (was: Unconfirmed)
I think this is a dup of a bug that was introduced with the switch to the url::Origin class. A fix for this is in and has been merged into M52.
►

Sign in to add a comment