After years of using marble, my cache somehow got a corrupted file. Marble then went into infinite loop and froze when cloud were enable. After some IRC discussion, I now upload the cloud folder in this bug for further investigation. It might be a good idea to shield marble against download corruption. Reproducible: Always Steps to Reproduce: 1. Open marble with the attached cached files 2. Select sat view 3. Zoom in and out from 0%-50% zoom level 4. Wait for a freeze Actual Results: Freeze Expected Results: No Freeze
Created attachment 76573 [details] Could file
It looks like the crash is caused by a corrupt 0 Byte tile clouds/1/000001/000001_000002.jpg This could always happen so if this is the reason it should get addressed. Another curious fact is this: * Level 0 tiles are from today * Level 1 tiles are from 2011 I still wonder how Level 1 tiles from 2011 can survive 2 years without getting updated.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!