| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007615 | Taler | wallet-core | public | 2023-01-29 09:48 | 2023-02-21 16:39 |
| Reporter | davidak | Assigned To | Florian Dold | ||
| Priority | high | Severity | block | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.9.1 | ||||
| Target Version | 0.9.2 | Fixed in Version | 0.9.2 | ||
| Summary | 0007615: Error contacting backend: Could not establish connection. Receiving end does not exist. | ||||
| Description | When i open the browser extension now, i get errors. How to get it to work again? In this state, selecting the checkbox to enable developer mode does nothing. When i reload the page, it is disabled. When loading the balance tab, the browser extension uses 2,2GB RAM and over 200% CPU (100% is one core). There still seem to be a transaction in progress from december, but you did reset the bank (i think) and my bank accounts don't exist, so there is no way this transaction will ever be finished. | ||||
| Steps To Reproduce | 1. Open browser extension 2. See errors | ||||
| Additional Information | Balance Could not load the list of transactions Error contacting backend: Could not establish connection. Receiving end does not exist. or Could not load the transaction information Error contacting backend: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received Dev Diagnostics timed out. Could not talk to the wallet backend. | ||||
| Tags | No tags attached. | ||||
|
|
Screenshot from 2023-01-29 09-53-13.png (111,303 bytes) |
|
|
The situation is resolved by FORGETing the transaction. You have to try multiple times to load the transaction page. |
|
|
This errors are related to this scenario: https://bugs.gnunet.org/view.php?id=7532 |
|
|
The issue you're describing is very likely a symptom of wallet-core being unresponsive while doing large withdrawals. Since the hanging/unresponsiveness issue is fixed now, you should not get this error anymore. |
