Nextcloud version 3.1.1git crashes when solving conflicts files with style Fusion or Chameleon on ArchLinux

[AkechiShiro]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Expected behaviour

Resolving conflicts should never crash Nextcloud.

Actual behaviour

Here is the backtrace I got in gef (an enhanced GDB)

Steps to reproduce

1. Have a lot of conflicts
2. Try to resolve them and then at some point
3. Notice the crash

Client configuration

Client version:

Nextcloud version 3.1.1git
Git revision 75c329f4ff3472774b00537e096ba8c987a6bb3c
Using Qt 5.15.2, built against Qt 5.15.2
Using Qt platform plugin 'xcb'
Using 'OpenSSL 1.1.1i  8 Dec 2020'
Running on Arch Linux, x86_64

Operating system: ArchLinux

OS language: English

Qt version used by client package (Linux only, see also Settings dialog):

Using Qt 5.15.2, built against Qt 5.15.2

Client package (From Nextcloud or distro) (Linux only): coming from distro, the community repo of the ArchLinux official repo

Installation path of client:/bin/nextcloud

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

1. Client logfile: the log file is huge about 58MB I can't really upload it anywhere at the moment.

I will upload the client log file later when reproducing the bug again.

[AkechiShiro]

Here is some more info, I'm adding the client logfile to the initial message of this issue.

Opening in existing browser session.
2021-01-07 18:02:51:376 [ fatal default ]:	Object 0x559f37ab7190 destroyed while one of its QML signal handlers is in progress.
Most likely the object was deleted synchronously (use QObject::deleteLater() instead), or the application is running a nested event loop.
This behavior is NOT supported!
qrc:/qml/src/gui/tray/Window.qml:550: function() { [native code] }
[1]    1282603 abort (core dumped)  nextcloud --logdebug --logfile log.txt

Edit: I couldn't upload the log file it is 58 MB in size, pretty big, gist just timeouts, I've tried other sites too with no luck, will provide it only if it is very necessary.

[er-vin]

Logs might not be necessary but the backtrace of the crash is definitely necessary. Thanks for that.

Looking at the backtrace you provided this doesn't seem to be related to the conflict dialog per say, more something with how and when the conflict notification is discarded from the list.

@allexzander you looked at this area last, rings any bell?

[Freeedim]

(Very sorry for the off-topic but I am trying to start a crusade the earliest I can against an error that seems quite new and quickly spreading across Internet, before it goes wild and viral:
"per say" does not exist and means nothing. "per se" does exist and is Latin for "by it(self)", or "in it(self)".
Sorry, I mean no offense.)

[er-vin]

(Very sorry for the off-topic but I am trying to start a crusade the earliest I can against an error that seems quite new and quickly spreading across Internet, before it goes wild and viral:
"per say" does not exist and means nothing. "per se" does exist and is Latin for "by it(self)", or "in it(self)".
Sorry, I mean no offense.)

Actually I'm more offended of the fact I did it... I'm very much aware of "per se"... I really wonder why I typed "say" this time. :-)