I’m pretty happy with Whisk otherwise.
1 Like
On a standard install with vanilla preferences this isn't reproducible, so it looks like it is likely a bug from some way Whisk is configured or a usage pattern that we haven't been able to find yet. (Basically under-the-hood some resources from a closed window are freed but the system technically thinks the window is still around, so we're trying to load new colors in an invalid state).
I'd be curious if you can reproduce this 100% of the time from a newly launched state? Or if there's certain steps you are aware that might make this trigger?
If not, I probably have some follow up questions about your configuration and usage patterns.
Thanks. I sent a crash report twice before, but I’ll send them every time now if you want. I can’t reproduce it on demand, but it happens on a regular basis with dark / light mode Appearance → Auto (I have to wait for the sun to go up or down).
(My Whisk Interface Preferences are the defaults.)
Does it crash if you use the System Settings Appearance option to switch between light or dark mode?
I just loaded up Whisk and put it in the background. I'm going to see if it explodes after sundown. 
It does sometimes, but for whatever reason it didn’t auto-crash last night or this morning, but then did today when I changed it from auto to dark.
Thanks for the additional information.
The crash log is good, it is extremely accurate on the point of the crash... but unfortunately that just points to the state of the app being "invalid" before the point of the crash.
I spent some time with this today using the preferences file you sent in, but under a variety of different circumstances couldn't reproduce it. I'm nearly certain it has to do with closing a window first -- if you never close any windows I don't think you'd ever hit this. But I can't figure out what operation is done in windows before closing that gets them in this state.
Perhaps you can give me some basic details on how you use Whisk and what your general flow is? Anything would help! Thanks 
.
I usually have at least one Whisk window open, and if it’s crashed with no windows, I don’t recall it.
Though, I think it may only happen if Whisk is ”inactive” (in the background), like, for example, if I switch to Safari.
I think the reason it didn’t auto-crash last night or this morning may be because I left Whisk “active” (in the foreground).
It may or may not have something to do with the Mac having slept after putting Whisk in the background.
I usually have the Whisk Web Preview open (attached), and I often hit Command-Return to open it in Safari.
And it may be a coincidence, but Whisk’s validator is out of date and doesn’t recognize light and dark meta theme-color or “light-dark” (among other things).
(I don’t usually have the inspector open, only the editor and preview.)
Thanks for the additional details. I'll try using that file (I just downloaded it from your site) and your settings and see if I can get it to reproduce similarly long-living.
The issue probably isn't in a state of windows closed, but in a state where at some point you have closed at least one window. Does that make sense?
(And yes, we will update the validator in the next release!)