View Issue Details

IDProjectCategoryView StatusLast Update
0007615Talerwallet-corepublic2023-02-21 15:39
Reporterdavidak Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityhighSeverityblockReproducibilityalways
Status closedResolutionfixed 
Product Version0.9.1 
Target Version0.9.2Fixed in Version0.9.2 
Summary0007615: Error contacting backend: Could not establish connection. Receiving end does not exist.
DescriptionWhen 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 Reproduce1. Open browser extension
2. See errors
Additional InformationBalance

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.
TagsNo tags attached.
Attached Files

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

davidak

2023-01-29 08:53

reporter   ~0019710

davidak

2023-01-29 08:59

reporter   ~0019711

The situation is resolved by FORGETing the transaction. You have to try multiple times to load the transaction page.

davidak

2023-01-29 09:01

reporter   ~0019712

This errors are related to this scenario: https://bugs.gnunet.org/view.php?id=7532

Florian Dold

2023-02-11 13:33

manager   ~0019801

Last edited: 2023-02-11 13:33

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.

Issue History

Date ModifiedUsernameFieldChange
2023-01-29 08:48davidakNew Issue
2023-01-29 08:48davidakStatusnew => assigned
2023-01-29 08:48davidakAssigned To => Florian Dold
2023-01-29 08:48davidakFile Added: Screenshot from 2023-01-29 09-28-57.png
2023-01-29 08:48davidakFile Added: Screenshot from 2023-01-29 09-28-45.png
2023-01-29 08:48davidakFile Added: Screenshot from 2023-01-29 09-42-55.png
2023-01-29 08:48davidakFile Added: Screenshot from 2023-01-29 09-35-44.png
2023-01-29 08:53davidakNote Added: 0019710
2023-01-29 08:53davidakFile Added: Screenshot from 2023-01-29 09-53-13.png
2023-01-29 08:59davidakNote Added: 0019711
2023-01-29 09:01davidakNote Added: 0019712
2023-01-30 13:03sebasjmPrioritynormal => high
2023-01-30 13:03sebasjmCategorywallet (WebExtensions) => wallet (TS core)
2023-01-30 13:03sebasjmProduct Version0.9 => 0.9.1
2023-01-30 13:03sebasjmTarget Version => 0.9.2
2023-02-11 13:33Florian DoldStatusassigned => informing
2023-02-11 13:33Florian DoldResolutionopen => fixed
2023-02-11 13:33Florian DoldNote Added: 0019801
2023-02-11 13:33Florian DoldNote Edited: 0019801
2023-02-21 15:39Christian GrothoffFixed in Version => 0.9.2
2023-02-21 15:39Christian GrothoffStatusinforming => closed
2023-04-13 18:36Florian DoldCategorywallet (TS core) => wallet-core