Exporting keys on EDR is painful.

[ara4n]

Steps to reproduce

1. Went to export megolm keys on EDR
2. After hitting the export button, the app spun 10 cores of CPU at 100% for 1 hour before saving (310MB) of keys
3. During this:

• i was able to edit the contents of the export dialogue (i.e. change the passphrase, and keep hitting export), which made me wonder if i'd actually hit export in the first place
• the console logged progress, which wasn't reflected anywhere in the dialog
• i gave up after about 30m and cancelled the dialog, but it didn't actually stop the export, which eventually coughed up the prompt to save the resulting file.

Outcome

What did you expect?

• Dialog to make it clear that it's exported, and disable editable controls
• Show export progress
• Cancelling dialog should cancel export
• Export should not chew 10 hours of CPU time

Operating system

No response

Application version

nightly

How did you install the app?

No response

Homeserver

No response

Will you send logs?

No

[t3chguy]

This looks like the closed issue #26681

[ara4n]

not really - on #26681 it failed to export.

Whereas here is does successfully export (if you wait an hour). But the UX has a tonne of other problems.

[t3chguy]

@ara4n the issue comments discuss whether to add a progress bar and claim that it worked quickly enough for you such that a progress bar is not needed

[ara4n]

i can believe there's overlap in the comments :) eitherway, let's use this one, given it's open

#24894 is related (but not the same) ftr