Repro:1. Click Tools > Collections2. Type the name of your collection, say "Test"; any random rules will do (I used type:bible lang:english)3. Click Search4. For type of search, click Bible5. Click Collection dropdown and select "Test"6. Click Tools > Collections again7. Click Open8. Right-Click on "Test" in the dropdown and select Delete (or hover over "Test" and click the X to the right)9. Click Search[Notice a problem already: "Test" shows as the collection to search in; but it doesn't exist anymore]10. Without changing that collection to something legitimate, execute a search; any search will doResult: CrashNote: This reproduced many times; a couple of times it didn't repro and the default collection on search after step 9 was set back to "Top Bibles" automatically. It seemed to be more likely to repro if I quit Logos after step 5 and then restarted it again, but I could often get it to repro without doing that.
Config: Windows Vista Ultimate SP2
How to Ask for Help | Logos Wiki | My Machine Specs | My Blog
This bug report might have gotten buried by the Gerda Pesswir spambot, so I'm bumping it up again to make sure someone from Logos sees it.
Rosie, Can you include a log file?
CTRL+click the logos icon to load the program. Perform your crash inducing steps and when it crashes, let whatever it does complete in order to save the log file.
Then upload the log file (Click the little film strip in the reply dialog here).
The log files are located in My documents/logos log files/*.log
Sarcasm is my love language. Obviously I love you.
I've been able to reproduce this scenario - though it seems a bit contrived.
Not sure how this would actually happen in daily use.
Here are my logs FWIW.
http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1803.Logos-Log-Files.zip
Thomas Black: I've been able to reproduce this scenario - though it seems a bit contrived.
"it seems a bit contrived" -- Ha! I remember telling that to the testers when I had to fix bugs in Microsoft Word before shipping... ;-)
Thomas Black: Not sure how this would actually happen in daily use.
It happened to me in the course of daily use, and I came up with a clearly reproducible case. I'm pretty sure what happened was I had tried out the collection feature just to learn how it worked, and didn't realized it had actually saved my dummy collection which I was just goofing around with. So when I noticed it was still there, I deleted it. Then, forgetting about that, I exited Logos. When I opened it back up again, and tried to execute a search, it crashed. I backtracked in my mind to what I'd been doing and figured out what had caused the crash and came up with those repro steps. There is no excuse for an application ever crashing, even if a user does something really boneheaded. It's probably an uninitialized variable in the code or someone trying to reference a null pointer, or something dumb like that. Good software testers do all kinds of sinister things to suss out these sorts of coding problems. I break software without thinking about it. I'm seriously not trying to be sinister. I just take it through its paces. I only wish I'd been able to get my hands on the beta more than two weeks before shipping, which is all the notice I had.
So, do you still need my log files now that you've reproduced it and uploaded your logs?
RosiePerera:It happened to me in the course of daily use
RosiePerera:There is no excuse for an application ever crashing, even if a user does something really boneheaded. It's probably an uninitialized variable in the code or someone trying to reference a null pointer, or something dumb like that. Good software testers do all kinds of sinister things to suss out these sorts of coding problems. I break software without thinking about it. I'm seriously not trying to be sinister. I just take it through its paces. I only wish I'd been able to get my hands on the beta more than two weeks before shipping, which is all the notice I had.
RosiePerera:So, do you still need my log files now that you've reproduced it and uploaded your logs?
TC...
I am following your every move hoping to see the 666
Philip Spitzer: TC... I am following your every move hoping to see the 666
I'm planning a double post to shoot right past it. Just because I know you're watching.
Philip Spitzer:I am following your every move hoping to see the 666
Well that didn't work out so good did it?
This crash is still present in SR6.
RosiePerera: This crash is still present in SR6.
I think this has already been fixed in the trunk (for 4.0a) but I'll make a note to double-check the bug database to ensure this was filed.
Bradley Grainger: RosiePerera: This crash is still present in SR6. I think this has already been fixed in the trunk (for 4.0a) but I'll make a note to double-check the bug database to ensure this was filed.
Just going back through old bug reports tying up some loose ends. This bug is definitely fixed. Not sure when it got fixed.