Opera 33.0.1990.58 crashes if logged in for symchronization
-
qpmmy last edited by
Hello. Here are the steps to reproduce my problem:
- Make a fresh install of opera-stable.
- Log in for synchronization.
- Close the browser.
- Launch it again.
- Opera crashes due to some problems with profile.
Console output is:
[1111/213348:ERROR:connection.cc(1340)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode = TRUNCATE
[1111/213349:ERROR:connection.cc(1340)] Web sqlite error 5, errno 0: database is locked, sql: PRAGMA cache_size=32
[1111/213349:ERROR:connection.cc(1340)] Web sqlite error 5, errno 0: database is locked, sql: SELECT COUNT(*) FROM sqlite_master
[1111/213349:ERROR:connection.cc(1340)] Web sqlite error 5, errno 0: database is locked, sql: CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY, value LONGVARCHAR)
[1111/213349:ERROR:web_database_backend.cc(54)] Cannot initialize the web database: 1
[1111/213349:ERROR:connection.cc(1340)] Passwords sqlite error 5, errno 0: database is locked, sql: PRAGMA journal_mode = TRUNCATE
[1111/213349:ERROR:desktop_window_tree_host_x11.cc(882)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType)
[1111/213350:ERROR:connection.cc(1340)] Passwords sqlite error 5, errno 0: database is locked, sql: PRAGMA cache_size=32
[1111/213350:ERROR:connection.cc(1340)] Passwords sqlite error 5, errno 0: database is locked, sql: CREATE TABLE meta(key LONGVARCHAR NOT NULL UNIQUE PRIMARY KEY, value LONGVARCHAR)
[1111/213350:ERROR:login_database.cc(399)] Unable to create the meta table.
[1111/213350:ERROR:password_store_default.cc(45)] Could not create/open login database.
Segmentation fault (core dumped) -
qpmmy last edited by
I found out that problem is actually in Opera not closing down properly. Sometimes its process keeps its presence in the background, so obviously when I try to launch an another instance, it crashes with the errors above. Also this background process, if not killed manually, causes current session's sort of inconsistency, so it takes too much time to then shutdown the system, like here:
