status-im / status-desktop

Status Desktop client made in Nim & QML
https://status.app
Mozilla Public License 2.0
298 stars 79 forks source link

Activity centre: Crash when receiving or accepting contact request from mobile #12702

Closed anastasiyaig closed 11 months ago

anastasiyaig commented 12 months ago

Description

Steps:

  1. Send contact request from mobile nightly to Desktop RC 15
  2. Observe the result on Desktop RC 15 side
INF 2023-11-13 13:58:38.362+03:00 starting application...                    topics="status-app" tid=1352816 file=nim_status_client.nim:204
WRN 2023-11-13 13:58:38.365+03:00 Error decoding signal                      topics="signals-manager" tid=1352816 file=signals_manager.nim:43 err="Unknown signal received: mediaserver.started"
Debug: StatusApplicationDelegate::applicationDidFinishLaunching (:0, )
ERROR[11-13|13:59:12.136|github.com/status-im/status-go/api/geth_backend.go:432] failed to initialize wallet db           package=status-go/api.GethStatusBackend err="failed to set `journal_mode` pragma: file is not a database"
failed to set `journal_mode` pragma: file is not a database
ERR 2023-11-13 13:59:12.136+03:00 error:                                     topics="accounts-service" tid=1352816 file=service.nim:665 procName=verifyDatabasePassword errDesription="failed to set `journal_mode` pragma: file is not a database"
WRN 2023-11-13 13:59:12.979+03:00 Error decoding signal                      topics="signals-manager" tid=1352816 file=signals_manager.nim:43 err="Unknown signal received: mediaserver.started"
INF 2023-11-13 13:59:18.239+03:00 initMailservers                            topics="mailservers-service" tid=1352816 file=service.nim:202 name=node-01.ac-cn-hongkong-c.status.prod nodeAddress=/dns4/node-01.ac-cn-hongkong-c.status.prod.statusim.net/tcp/30303/p2p/16Uiu2HAkvEZgh3KLwhLwXg95e5ojM8XykJ4Kxi2T7hk22rnA7pJC
INF 2023-11-13 13:59:18.239+03:00 initMailservers                            topics="mailservers-service" tid=1352816 file=service.nim:202 name=node-01.gc-us-central1-a.status.prod nodeAddress=/dns4/node-01.gc-us-central1-a.status.prod.statusim.net/tcp/30303/p2p/16Uiu2HAkwBp8T6G77kQXSNMnxgaMky1JeyML5yqoTHRM8dbeCBNb
INF 2023-11-13 13:59:18.239+03:00 initMailservers                            topics="mailservers-service" tid=1352816 file=service.nim:202 name=node-01.do-ams3.status.prod nodeAddress=/dns4/node-01.do-ams3.status.prod.statusim.net/tcp/30303/p2p/16Uiu2HAm6HZZr7aToTvEBPpiys4UxajCTU97zj5v7RNR2gbniy1D
INF 2023-11-13 13:59:18.241+03:00 initMailservers                            topics="mailservers-service" tid=1352816 file=service.nim:202 name=node-02.ac-cn-hongkong-c.status.prod nodeAddress=/dns4/node-02.ac-cn-hongkong-c.status.prod.statusim.net/tcp/30303/p2p/16Uiu2HAmFy8BrJhCEmCYrUfBdSNkrPw6VHExtv4rRp1DSBnCPgx8
INF 2023-11-13 13:59:18.241+03:00 initMailservers                            topics="mailservers-service" tid=1352816 file=service.nim:202 name=node-02.do-ams3.status.prod nodeAddress=/dns4/node-02.do-ams3.status.prod.statusim.net/tcp/30303/p2p/16Uiu2HAmSve7tR5YZugpskMv2dmJAsMUKmfWYEKRXNUxRaTCnsXV
INF 2023-11-13 13:59:18.241+03:00 initMailservers                            topics="mailservers-service" tid=1352816 file=service.nim:202 name=node-02.gc-us-central1-a.status.prod nodeAddress=/dns4/node-02.gc-us-central1-a.status.prod.statusim.net/tcp/30303/p2p/16Uiu2HAmDQugwDHM3YeUp86iGjrUvbdw3JPRgikC7YoGBsT2ymMg
INF 2023-11-13 13:59:18.247+03:00 fetch mailservers                          topics="mailservers-service" tid=1352816 file=service.nim:208 rpc_proc=mailservers_getMailservers response="(jsonrpc: \"2.0\", result: null, id: 0, error: nil)"
ERR 2023-11-13 13:59:19.787+03:00 rpc response error                         topics="rpc" tid=1352816 file=core.nim:36 err="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:19.788+03:00 error doing rpc request                    topics="rpc" tid=1352816 file=core.nim:40 methodName=ens_getName exception="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:19.788+03:00 error:                                     topics="wallet-account-service" tid=1352816 file=utils.nim:109 errDesription="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:20.861+03:00 rpc response error                         topics="rpc" tid=1352816 file=core.nim:36 err="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:20.861+03:00 error doing rpc request                    topics="rpc" tid=1352816 file=core.nim:40 methodName=ens_getName exception="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:20.861+03:00 error:                                     topics="wallet-account-service" tid=1352816 file=utils.nim:109 errDesription="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:21.910+03:00 rpc response error                         topics="rpc" tid=1352816 file=core.nim:36 err="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:21.910+03:00 error doing rpc request                    topics="rpc" tid=1352816 file=core.nim:40 methodName=ens_getName exception="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:21.910+03:00 error:                                     topics="wallet-account-service" tid=1352816 file=utils.nim:109 errDesription="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
2023-11-13T13:59:22.275+0300    INFO    communities/manager.go:308  initializing history archive tasks
ERR 2023-11-13 13:59:23.053+03:00 rpc response error                         topics="rpc" tid=1352816 file=core.nim:36 err="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:23.053+03:00 error doing rpc request                    topics="rpc" tid=1352816 file=core.nim:40 methodName=ens_getName exception="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
ERR 2023-11-13 13:59:23.054+03:00 error:                                     topics="wallet-account-service" tid=1352816 file=utils.nim:109 errDesription="\nstatus-go error [methodName:ens_getName, code:-32000, message:not a resolver ]\n"
SIGSEGV: Illegal storage access. (Attempt to read from nil?)
zsh: segmentation fault  ./nim_status_client -d:~/data/RC

https://github.com/status-im/status-desktop/assets/82375995/46953557-bc00-41d7-b2e7-f3ecc9d18f4c

MishkaRogachev commented 12 months ago

Tried dev builds (RC 0.15 and master branches) and RC 0.15 with main acc, seems to work for me.. https://github.com/status-im/status-desktop/assets/2522130/36b5105b-1fd6-4092-90a4-4deaad3d3417

Screenshot 2023-11-14 at 16 18 59 Screenshot 2023-11-14 at 16 19 04
anastasiyaig commented 12 months ago

@churik maybe you can help reproducing?

jrainville commented 12 months ago

It's quite possible that this issue was the same as the other crash. When receiving the contact request, we probably tried to process the profile showcase and if there was none, it crashed. That has been fixed, so maybe it's why it's not reproducible in master or the release branch.

@MishkaRogachev can you try the repro steps but with a commit prior to the fix?

MishkaRogachev commented 12 months ago

It's quite possible that this issue was the same as the other crash. When receiving the contact request, we probably tried to process the profile showcase and if there was none, it crashed. That has been fixed, so maybe it's why it's not reproducible in master or the release branch.

@MishkaRogachev can you try the repro steps but with a commit prior to the fix?

sure, trying 3b06ae589370bb3155276730c1115c0787832903

MishkaRogachev commented 12 months ago

@MishkaRogachev can you try the repro steps but with a commit prior to the fix?

I expected this version to crash, but it also works. Today i have a long delay between sending and receiving the CR. And i got a few random crashes i'm trying to investigate now.

Screenshot 2023-11-15 at 18 16 33
MishkaRogachev commented 11 months ago

UPD: there is a possibility i've faced https://bugreports.qt.io/browse/QTBUG-92236, ill upgrade Qt and test again

churik commented 11 months ago

It is not reproducible between Desktop RC and Mobile RC, can be closed

anastasiyaig commented 11 months ago

okay perfect lets close it