https://bugs.kde.org/show_bug.cgi?id=439664
Méven Car <meve...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DOWNSTREAM
Status|CONFIRMED |RESOLVED
--- Comment #22 from Méven Car <meve...@gmail.com> ---
(In reply to Henrique Sant'Anna from comment #21)
> Dolphin can (or should) handle the plugin error and prevent the entire
> application from shutting down.
This is technically impossible, or it would require to rewrite all the plugins
in the first place and do even more work of the dolphin side as well.
Other plugins are fine.
>
> The application is closing because its code does not anticipate that plugins
> can perform actions that result in a fatal error.
The application crashes because the plugin is buggy and unmaintained.
And since those are C++ plugins they leave in the same processes and can't
survive a crash of one another.
I can add the bug seems like an easy one to fix. That I may have help fix but
its development is not open.
There is an old version of its code online:
https://github.com/insynchq/dolphin-insync-plugin/blob/master/dolphin-insync-plugin.cpp
Please direct your feedback to the company concerned:
https://forums.insynchq.com/t/insynch-crashing-dolphin/18686
In comparison a nextcloud or owncloud develop and maintain well their dolphin
plugin.
>
> There are multiple errors that Dolphin itself can cause, but these errors
> are handled in such a way that they do not result in failure.
Sure, applications dev follows this mind-set, for instance by prioritizing
frequent crashing issues.
Plugins should do the same, but it requires resources as anything to make
progress.
--
You are receiving this mail because:
You are watching all bug changes.
