{"action":"created","issue":{"url":"https://api.github.com/repos/paritytech/parity/issues/5474","repository_url":"https://api.github.com/repos/paritytech/parity","labels_url":"https://api.github.com/repos/paritytech/parity/issues/5474/labels{/name}","comments_url":"https://api.github.com/repos/paritytech/parity/issues/5474/comments","events_url":"https://api.github.com/repos/paritytech/parity/issues/5474/events","html_url":"https://github.com/paritytech/parity/issues/5474","id":222744203,"number":5474,"title":"Parity crash during launch. ","user":{"login":"Ochir","id":3234919,"avatar_url":"https://avatars3.githubusercontent.com/u/3234919?v=4","gravatar_id":"","url":"https://api.github.com/users/Ochir","html_url":"https://github.com/Ochir","followers_url":"https://api.github.com/users/Ochir/followers","following_url":"https://api.github.com/users/Ochir/following{/other_user}","gists_url":"https://api.github.com/users/Ochir/gists{/gist_id}","starred_url":"https://api.github.com/users/Ochir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ochir/subscriptions","organizations_url":"https://api.github.com/users/Ochir/orgs","repos_url":"https://api.github.com/users/Ochir/repos","events_url":"https://api.github.com/users/Ochir/events{/privacy}","received_events_url":"https://api.github.com/users/Ochir/received_events","type":"User","site_admin":false},"labels":[{"id":554224054,"url":"https://api.github.com/repos/paritytech/parity/labels/Z0-intended","name":"Z0-intended","color":"ffffff","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2017-04-19T13:47:28Z","updated_at":"2017-09-20T23:36:51Z","closed_at":"2017-04-25T11:06:14Z","author_association":"NONE","body":"We wrote a lot of different data to blockchain. \r\nRecently, after new portion of data, parity became to crash with the following output:\r\n\r\n     parity --chain morden-new.json --jsonrpc-hosts all --rpcaddr all --rpccorsdomain \"*\" --usd-per-tx 0 --force-sealing --keys-path batch/parity-$port/keys --db-path batch/parity-$port/db --base-path batch/parity-$port --no-ui --no-dapps --rpcport $rpcport --port $port --no-ipc --engine-signer $account --password pp --fast-and-loose -lown_tx,sync=debug --log-file load1.log1\r\n    2017-04-19 16:36:31  main INFO parity::run  Starting Parity/v1.6.6-beta-8c6e3f3-20170411/x86_64-linux-gnu/rustc1.16.0\r\n    2017-04-19 16:36:31  main INFO parity::run  State DB configuration: fast\r\n    2017-04-19 16:36:31  main INFO parity::run  Operating mode: active\r\n    2017-04-19 16:36:31  main INFO ethcore::service  Configured for Muuu using AuthorityRound engine\r\n    thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/option.rs:323\r\n    stack backtrace:\r\n       1:     0x55ef8dced90c - <unknown>\r\n       2:     0x55ef8dcf4dfe - <unknown>\r\n       3:     0x55ef8dcf4a04 - <unknown>\r\n       4:     0x55ef8dcf529b - <unknown>\r\n       5:     0x55ef8dcf5134 - <unknown>\r\n       6:     0x55ef8dcf5059 - <unknown>\r\n       7:     0x55ef8dcf4fe7 - <unknown>\r\n       8:     0x55ef8dd21cdd - <unknown>\r\n       9:     0x55ef8dd21c14 - <unknown>\r\n      10:     0x55ef8d91ea5f - <unknown>\r\n      11:     0x55ef8d82fdfd - <unknown>\r\n      12:     0x55ef8d85fb32 - <unknown>\r\n      13:     0x55ef8d3b638b - <unknown>\r\n      14:     0x55ef8d3d5828 - <unknown>\r\n      15:     0x55ef8d3dc7aa - <unknown>\r\n      16:     0x55ef8d3df475 - <unknown>\r\n      17:     0x55ef8dcfbebb - <unknown>\r\n    Aborted (core dumped)\r\n\r\nI would want to debug it deeply if I knew how to do it. \r\nI have an idea that our new portion of data somehow corrupt DB but I have no idea how to check it. \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/paritytech/parity/issues/comments/331010098","html_url":"https://github.com/paritytech/parity/issues/5474#issuecomment-331010098","issue_url":"https://api.github.com/repos/paritytech/parity/issues/5474","id":331010098,"user":{"login":"sleepndevelop","id":22989619,"avatar_url":"https://avatars1.githubusercontent.com/u/22989619?v=4","gravatar_id":"","url":"https://api.github.com/users/sleepndevelop","html_url":"https://github.com/sleepndevelop","followers_url":"https://api.github.com/users/sleepndevelop/followers","following_url":"https://api.github.com/users/sleepndevelop/following{/other_user}","gists_url":"https://api.github.com/users/sleepndevelop/gists{/gist_id}","starred_url":"https://api.github.com/users/sleepndevelop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sleepndevelop/subscriptions","organizations_url":"https://api.github.com/users/sleepndevelop/orgs","repos_url":"https://api.github.com/users/sleepndevelop/repos","events_url":"https://api.github.com/users/sleepndevelop/events{/privacy}","received_events_url":"https://api.github.com/users/sleepndevelop/received_events","type":"User","site_admin":false},"created_at":"2017-09-20T23:36:51Z","updated_at":"2017-09-20T23:36:51Z","author_association":"NONE","body":"Restarted my PC and still crashes, and i'm not using --fast-and-loose.\r\n\r\nIs there a verbose mode option to write a more detailed log and easily spot the bugs?\r\nOr can you implement it in a next release?"}}
{"actor":{"display_login":"sleepndevelop"}}