-
Notifications
You must be signed in to change notification settings - Fork 100
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
Tab crashing when moving task in Chrome / Brave: RESULT_CODE_KILLED_BAD_MESSAGE
#2666
Comments
Getting the same issue here. Works fine on Firefox, crashes on Chrome and Edge. Chrome log below:
|
Crashes on brave too (which isn't surprising as it's chromium based) |
can confirm issue on brave |
I can confirm this on brave |
It's unfortunately making the app pretty much useless for me. I'm happy with using planify but there's no webui |
Same issue, seems to be a
|
Can confirm - Works in Firefox - Chrome browsers broken. |
Can confim. All above are correct. Trying to drag a task in Chrome, Edge or Vivaldi crashes browser window. Dragging works in Firefox, though. Tried on 3 different Windows computers. Problem exists on both NextCloud 27.1.3 on self-hosted, manually installed Ubuntu 20.04 server and 29.0.7 on an up-to-date Cloudron server. All plugins are updated. I cleared my browser cache and cookies. Closed everything, restarted my computer. |
like @suly520 I have 404 on 'tasks-Plus.css' and 'tasks-store.css' but not for 'task-main.css'. (Fails on Brave, not on Firefox) |
I can confirm, that Chrome crashes directly after the drag started. I think this is a Chrome issue, as it used to work in the past. I will check how we can work around this. |
I think it is unlikely that this causes an issue. However, this problem was fixed in #2667 and will be included in the next release. |
Second that: Issue of crashing tab remains after I applyed those changes to my local copy. Just got rid of the 404 in network console. |
Did some tests with older versions of Chrome, seems it started to fail with versions > 128.x.x.x. |
Same with Opera (114.0.5282.21) using Chromium (128.0.6613.162) |
Same with Brave 1.70.126 based on Chromium 129.0.x |
Confirming the issue on Chrome 131.0.6778.24 (Officiële build) beta (64-bits) |
Does this happen to previous version of tasks or nextcloud? I've just noticed this bug today after updating nc from 27.x to 27.1.11. It could have been there already and I did not notice. |
I use Tasks on murena.io (/e/ cloud) and at the moment they are using nc 28. The problem suddently appeard a while back to me and I didn't look at the version they where using back then. |
RESULT_CODE_KILLED_BAD_MESSAGE
Same issue for me... Any information on when it could be fixed? |
Again, this bug was introduced by Chromium / Chrome. So the proper place to report it is the Chromium project. I just tried with Chromium 121.0.6111.0 from 6 Nov 2023 where dragging a task works fine. With the a current version Chromium 133.0.6844.0 from 18 Nov 2024 dragging crashes the window. The best we can hope for from our side is that we find a workaround. The only proper solution is a Chromium fix imho. And regarding the deleted comment from above:
I second this, but please replace Nextcloud / Tasks with Google / Chrome. |
Steps to reproduce
Expected behavior
Subtask moved
Actual behaviour
Chrome tab crashing: Error code: RESULT_CODE_KILLED_BAD_MESSAGE
Tasks app version
0.16.1
CalDAV-clients used
No response
Browser
Chromium 128 Arch Linux / Chrome 128 Windows 10
Client operating system
No response
Server operating system
Arch Linux
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
29.0.5-1
Updated from an older installed version or fresh install
None
List of activated apps
No response
Nextcloud configuration
No response
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
I think this might be a Chrome issue - feel free to close. Other browsers tested and working fine: Firefox, Qutebrowser. Can somebody reproduce?
Might this relate? https://stackoverflow.com/questions/74714574/chrome-tab-breaks-with-result-code-killed-bad-message-when-service-worker-tries
The text was updated successfully, but these errors were encountered: