-
Notifications
You must be signed in to change notification settings - Fork 210
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
Fix some main loop crashes #2008
Conversation
what about https://github.com/KomodoPlatform/atomicDEX-Desktop/blob/dev/src/core/atomicdex/models/qt.portfolio.model.cpp#L157 ? can you enable that log line too? because i fear that this task takes a much too long time... you can also see this when you have 200 coins enabled and simply stay on portfolio page, the app will stall for couple seconds from time to time... and i suspect it does in this task |
Done |
Please test whenever you have time, the CI builds in debug mode so if you can run your testing session with gdb/lldb or any other debugger it will help me catch where are the problems Also Ubuntu CI seems broken I cannot make it build in debug, if someone can help me :) |
For
This one failed because Github has CI brownouts periodically to remind users to update before 18.04 is EOL. Give 20.04 a shot. |
there are several changes needed to make it compile under ubuntu 22.04... the above error comes from this package: https://github.com/KomodoPlatform/atomicDEX-Desktop/blob/dev/ci_tools_atomic_dex/ci_scripts/linux_script.sh#L28 but there is more... had to add btw, my builds are made with 20.04 since a long time, so i already use ADEX Desktop compiled for 20.04: https://github.com/cipig/atomicDEX-Desktop/blob/nogeo/.github/workflows/atomicdex-desktop-ci.yml#L32 |
oh, doesn't compile for ubuntu any more:
|
It's weird, CMake wrote twice |
i managed to make it crash... it was running in the background... this are the last entries in log file/console:
btw, where does |
got a new one
looks like this one is related to bad internet... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Progress has been made, and it seems the remaining problems are likely related to pre-existing problems related to #2026
App is sufficiently stable for release and we can tackle the cpprestsdk issues in next iteration as it is too large a task to complete before 0.5.7
agree, i had no hard crash with this in the last time |
Related to #2002