I’m not sure of a consistent method of reproducing this bug, as I am unaware of what causes the app to crash. However, how the app handles the crash is honestly one of the most frustrating user experiences I’ve had to endure.
OS: Windows 7 Professional (64-bit)
Processor: Intel Core i7-4770 CPU @ 3.40GHz
RAM: 32.0 GB
Integrated graphics card: Intel HD Graphics 4600
Note: I had 4 different projects open when the crash occurred.
What happens after app crashes / stops responding:
Balsamiq 3 process continues to run after I close out of the program, so I have to kill it through Task Manager. Otherwise, I cannot re-open Balsamiq (attempting to open a BMPR file without killing the process first results in nothing happening).
After I kill the process in Task Manager, then I can re-open the BMPR file. If, however, I had multiple files open in prior to the crash, then all of the files will re-open. This is understandable, as I know this behavior occurs when re-launching a crashed browser (the browser will attempt to open up all of the tabs that you had prior to the crash). But it’s frustrating because, after all files have been opened, they’re all buggy!
If I then close all of the files, kill the process again, and re-launch, the app still attempts to open all the pre-crash files. And it still remains buggy.
Perhaps the most frustrating bug is that if you left-click on any element and then try to click off of it by clicking on any of part of the canvas, then the focus remains on the clicked element. This bug happens every time the app crashes and then is re-launched.
Additionally, keyboard functionality that normally works suddenly becomes limited. E.g., if I focus on an element, I cannot then use the DELETE button to delete the element. I can, however, click on the built-in trash icon to delete the item. Ctrl-Z also ceases to undo moves.
On some occasions (not always), after I try to re-launch and then close out of the now bug-ridden app, I get a weird blank Balsamiq screen. This screen can’t be closed anymore unless I kill the process; it just hangs there. See image below:
Once I kill the process, re-launch Balsamiq 3, and have all of the files auto-open again, then if I were to click on another BMPR file to open it up, all the toolbar icon does is flash that yellow / orange notification color; the file that I attempted to open does not open. (I see that someone else has mentioned this bug as well: “Balsamiq 3 sometimes won’t open after if freezes and I force quit the application”)
Now, here’s the worst part of it all: even after I restart my computer, the bugs described above almost always persist. As in, I’ll re-open one of my BMPR files, and then all of the files that were open pre-crash will still continue to open. The left-click behavior is still messed up; the keyboard functionality is still limited; the blank screen may continue to appear; files may continue to refuse to open properly.
Balsamiq crashes actually occur more than once a week for me, since I work in it so much. Please, for the love of my sanity, fix it so it handles crashes better than it currently does!