https://bugs.gpodder.org/show_bug.cgi?id=1142
--- Comment #9 from flan_suse <[email protected]> 2011-09-28 15:15:14 BST --- (In reply to comment #8) > Is this basically the same as bug 1040? No. These two bugs seem similar, but they are different. The bug referenced above, 1040, I could not reproduce with the "tres" branch. > Is it still an issue in gPodder 2.19 and/or the "tres" branch in Git? Yes. I can still crash gPodder on the "tres" branch with this bug. In fact, I've discovered how to make it crash every single time. The reason users might not see this happen often, if at all, is because it's a matter of unfortunate timing. Here's how to reproduce the crash, even on the latest in the "tres" branch: 1) Select a subscription with plenty of episodes (more than 10 is good, but the number is not very important). 2) Click the "Check for Updates" button. QUICKLY MOVE ON TO STEP 3! 3) This is crucial: *While* it is checking all your subscriptions for updates, click and drag to *highlight* a bunch of episodes and *stop* your mouse cursor from moving *before* it finishes checking for updates. Now just wait until it finishes checking for updates, and upon doing so, gPodder will crash. (During this time, you must not let go of your mouse button.) 4) Crazy, yeah? I have no clue how I stumbled upon this glitch. 5) I'll post a debug log if it helps. 6) I'll stop numbering all my lines now. -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
