AkkomaGang/akkoma-fe

Fork 62

[bug] Akkoma is crashing Chrome 125 when Application tab in DevTools is open #395

New issue

Closed

opened 2024-05-25 08:03:44 +00:00 by lamp · 4 comments

lamp commented

2024-05-25 08:03:44 +00:00

Version

efb46fc2

What were you trying to do?

Clear the drafts in localStorage because of another bug in Akkoma

What did you expect to happen?

nothing?

What actually happened?

Apparently Chrome crashes whenever the Application tab in Developer Tools is open on any Akkoma instance (i.e. akko.wtf, akko.unix.dog), whether logged in or not. Does not happen with Pleroma or any other site. Did not happen on Chrome 124 but does happen on Chrome 125 (125.0.6422.113, 125.0.6422.60). OS: Windows 10 x86_64, macOS 14.5 arm64, Linux 5.15.0 x64_64

Severity

I cannot use it as easily as I'd like

Have you searched for this issue?

I have double-checked and have not found this issue mentioned anywhere.

### Version efb46fc2 ### What were you trying to do? Clear the drafts in localStorage because of another bug in Akkoma ### What did you expect to happen? nothing? ### What actually happened? Apparently Chrome crashes whenever the Application tab in Developer Tools is open on any Akkoma instance (i.e. akko.wtf, akko.unix.dog), whether logged in or not. Does not happen with Pleroma or any other site. Did not happen on Chrome 124 but does happen on Chrome 125 (125.0.6422.113, 125.0.6422.60). OS: Windows 10 x86_64, macOS 14.5 arm64, Linux 5.15.0 x64_64 ### Severity I cannot use it as easily as I'd like ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.

lamp referenced this issue

2024-05-25 08:19:42 +00:00

[bug] Uploading a BMP file bricks the frontend #396

Oneric commented

2024-05-26 03:30:06 +00:00

Member

Crashing the whole browser is far beyond what any website is (supposed to be) capable of; this is definitely a Chromium bug and you should report it there.

Fyi, the relevant part seems to be a misuse of std::string::pop_back:

/usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/basic_string.h:2131: void std::basic_string<char>::pop_back() [_CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]: Assertion '!empty()' failed.

Crashing the whole browser is far beyond what any website is (supposed to be) capable of; this is definitely a Chromium bug and you should report it there. Fyi, the relevant part seems to be a misuse of `std::string::pop_back`: ``` /usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/bits/basic_string.h:2131: void std::basic_string<char>::pop_back() [_CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]: Assertion '!empty()' failed. ```

~~Oneric referenced this issue from AkkomaGang/akkoma 2024-05-26 03:30:41 +00:00~~

meta: closeable issues #758

Oneric referenced this issue from AkkomaGang/akkoma

2024-05-26 03:32:02 +00:00

meta: closeable issues #758

lamp commented

2024-05-26 06:17:30 +00:00

Author

do u have any idea why only akkoma crashes it and not pleroma or anything else?

floatingghost commented

2024-05-26 13:28:26 +00:00

Owner

that's hard to say, but browser tabs are sandboxed in such a way that it should be impossible for any site to interact with the host machine, including crashing the process

you'd need to be able to debug chromium to figure that out

that's hard to say, but browser tabs are sandboxed in such a way that it should be impossible for any site to interact with the host machine, including crashing the process you'd need to be able to debug chromium to figure that out

floatingghost closed this issue

2024-05-26 13:28:26 +00:00

Oneric commented

2024-05-26 15:21:59 +00:00

Member

btw this was already reported to Chromium (for a site different from akkoma-fe): https://issues.chromium.org/issues/342802973 (and probably also 342701249)