Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web UI has crashed, Transfers tab. Page refresh = working again #422

Closed
slrslr opened this issue Jun 19, 2022 · 1 comment
Closed

Web UI has crashed, Transfers tab. Page refresh = working again #422

slrslr opened this issue Jun 19, 2022 · 1 comment

Comments

@slrslr
Copy link

slrslr commented Jun 19, 2022

Current UI and client versions:

Application version AirDC++w 2.11.2 x86_64
Web UI version 2.11.2

Operating system:

Linux Debian 11, Firefox-ESR 91.10

Steps to reproduce the issue:

I was on Transfers tab for some hours

ISSUE

Not sure if is good for you that i create another issue for "Web UI has crashed", here it is:

Web UI has crashed

Please submit a bug report with the requested information (and the crash details below) at the [issue tracker](https://github.com/airdcpp-web/airdcpp-webclient/issues).
Crash details

i@https://127.0.0.1:5601/js/424.b407aaf3218fa480b144.chunk.js:1:8331
oa@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2258689
Rs@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2310894
kA@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2298103
BA@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2298031
vA@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2297892
fA@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2294879
Gn/<@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2244587
60053/t.unstable_runWithPriority@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2665854
Yn@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2244364
Gn@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2244534
Wn@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2244467
AA@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2292258
Ea@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2263987
li</n</</t</<@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:3055730
i@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2648897
80179/n.prototype.emit@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2659164
68656/t.trigger@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2649188
_onSessionUpdated@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2946208
17187/r.prototype.emit@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:1713151
handleMessage@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2926241
S@https://127.0.0.1:5601/js/main.d64158ea2453985dde98.entry.js:2:2930362

after page refresh i see UI again working (possibly due to me having auto-run script if process disappear)

@maksis maksis added the bug label Oct 25, 2022
@maksis
Copy link
Member

maksis commented Oct 25, 2022

Most likely a duplicate of #412

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants