[11884:11884:1124/100026.279256:ERROR:validation_errors.cc(122)] Invalid message: VALIDATION_ERROR_DESERIALIZATION_FAILED
[11884:11884:1124/100026.279269:ERROR:render_process_host_impl.cc(5850)] Terminating render process for bad Mojo message: Received bad user message: Validation failed for blink.mojom.LocalFrameHost.87 [VALIDATION_ERROR_DESERIALIZATION_FAILED]
[11884:11884:1124/100026.279275:ERROR:bad_message.cc(31)] Terminating renderer for bad IPC message, reason 123
[1124/100026.303897:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1124/100026.305936:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[1124/100026.316247:ERROR:process_memory_range.cc(75)] read out of range
[1124/100026.316256:ERROR:process_memory_range.cc(75)] read out of range
[11884:11884:1124/100026.335805:ERROR:interface_endpoint_client.cc(725)] Message 1640861540 rejected by interface blink.mojom.LocalFrameHost
Getting the same problem in Brave
Version 1.73.91 Chromium: 131.0.6778.85 (Official Build) unknown (64-bit) on Kbuntu Linux 24.04.
This is most likely a problem with the Chromium engine but it would be interesting to understand how Nextcloud Tasks is triggering it with the drag and drop in order to isolate the cause for the Chromium devs.
Is anything being done about this? It’s been 5 months since I started experiencing this. We can’t use the Task Manager at our office unless we force everyone to start using Firefox, which obviously is not a realistic option.
The Stack Overflow post you referenced describes a scenario where Chrome crashes with the error code RESULT_CODE_KILLED_BAD_MESSAGE when a service worker attempts to cache requests containing headers with UTF-8 characters, such as ‘ü’. This issue arises because, according to HTTP specifications, certain characters are not permitted in header fields, and their presence can lead to unexpected browser behavior, including crashes. Stack Overflow
While the exact cause of the drag-and-drop crash in Chrome-based browsers hasn’t been definitively identified, it’s plausible that a similar issue is at play. If the drag-and-drop functionality involves JavaScript operations that introduce invalid characters into HTTP headers or other critical data structures, it could trigger the observed crashes.
Potential Solutions:
Investigate Header Content: Developers should examine the headers involved in the drag-and-drop operations to ensure they comply with HTTP standards, avoiding any invalid characters that could destabilize the browser.Stack Overflow
Base64 encoding: Does NC use Base64 encoding for data transmitted in headers? This can prevent the inclusion of problematic characters.
Collaborate with Browser Developers: Reporting these findings to the Chromium development team can facilitate a deeper investigation, potentially leading to browser-level fixes that prevent such crashes in the future.
Update Dependencies: Ensuring that all libraries and dependencies used by Nextcloud Tasks are up-to-date can mitigate compatibility issues that might lead to such crashes.
NC uses Sortable for the Task manager, so I checked the Sortable website (SortableJS) to make sure it works in Chrome and Vivaldi and all the components shown on the home page do, so there must be something about the implementation in NextCloud that is causing the issue. I don’t personally think it’s a Chomium issue. I think NextCloud needs to spend more time on this because without a task manager I can’t see people recommending this package for use in a business.