-
Notifications
You must be signed in to change notification settings - Fork 671
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
crash on remove account #9367
Comments
from the logs: |
Yay a crash, shouldn't we get a backtrace? |
Yup. It was a crash. AUT coredump is still not printed in the log because of #9259. I will look into the fixing apport problem so that this unavailability of AUT crash log does not happen again. |
happened again today https://drone.owncloud.com/owncloud/client/10411/3/14 |
Failed again today https://drone.owncloud.com/owncloud/client/10514/3/14 |
@Talank Any idea what happens here and what we could do? |
Well, we do have the squish backtrace in the log. But clearly it is an AUT crash causing the connection lost error. We can start investigating from the log that we already have, but I highly doubt that there will be any other outcomes from that investigation. The backtracking works perfectly in local test runs so we can try to reproduce it locally, which might give us some additional idea (if we can reproduce it). |
@TheOneRing I reproduced the issue locally. Here is the full backtrace |
The crash seems to occur in line 166. client/src/gui/activitywidget.cpp Lines 164 to 168 in 105d39c
And then when accessing the shared ptr client/src/gui/accountstate.cpp Line 145 in 105d39c
|
@TheOneRing Talank took off the QA-team label. Please reach out if you need more help here |
remove an account connection
scenario fails
@Talank can you pls describe the necessary steps? |
@TheOneRing I reproduced the crash by running the automated test
|
A change was merged and the issue is hopefully fixed. |
I ran the test (more than 20 times) that reproduced the crash. And I am not being able to reproduce it anymore in 2.10 branch. So I agree that the issue is hopefully fixed. |
Thx |
I noticed the crash again in #9518 (comment) and in #9525 (comment) |
I just tried to reproduce the issue and capture it with a debugger following the steps listed in #9367 (comment). In over 40 repetitions, I couldn't produce a crash, thus I cannot tell where the crash occurs. How should we proceed with this issue? |
Earlier, in #9367 (comment) I reproduced it by running the automated test (that captured the crash) more than 20 times continuously. |
This comment was marked as off-topic.
This comment was marked as off-topic.
We now have stacktraces from the CI builds, see #9555 (comment). The stacktrace linked from there:
The |
happened again on 14.05 |
Please retest on master, we don't expect another 2.10 release |
fixed on master |
We have seen this error message before, and haven't seen it in a while. However, we need to investigate why it is failing. Since no changes has been merged, and it failed in only one of the nightly build during the weekend, it clearly is a flaky test.
The error details filtered by our log parser is as follows:
Related drone run (failing): https://drone.owncloud.com/owncloud/client/10363/3/14
The text was updated successfully, but these errors were encountered: