Program has become unusable

Bug Reports
1

Observed behavior

The program appears in the windows 11 taskbar, but the preview when hovering over the taskbar icon only shows a white screen. When clicking on the program the application window never appears. It’s using about 1.08gb of ram while the program is running. I’ve tried force quitting the program, reinstalling it, and restarting my system, but none have had any effect.

Expected behavior

When I click on the application it opens and I’m able to see the application window.

Steps required to reproduce

  1. I moved photos into the aspect root directory using the file browser, then the issue started appearing.

Operating system/Hardware used

Microsoft Windows 11 Pro
Version 10.0.26100 Build 26100
Processor 12th Gen Intel(R) Core™ i7-1255U, 1700 Mhz, 10 Core(s), 12 Logical Processor(s)
16gb RAM

2

Do the application window contents appear at all, so that it at least briefly shows the “loading library” status, or does it immediately enter this apparently unresponsive state?

If you have the possibility, can you send me a copy of the log file at the moment this is happening to bugs@bildhuus.com? I can see a crash report from two days ago where a crash appears to have happened after the computer went into standby mode, but I don’t think that this is related.

There are a few files/folders that you can try to remove to see if they are responsible:

  • %LOCALAPPDATA%\Bildhuus\Aspect\globalcache
  • %LOCALAPPDATA%\Bildhuus\Aspect\jitcache
  • %APPDATA%\Bildhuus\Aspect\app.settings

Where %APPDATA% typically is at C:\Users\<username>\AppData\Roaming and %LOCALAPPDATA% is at C:\Users\<username>\AppData\Local. I would recommend to just move those files/folders to somewhere else first, instead of directly deleting it, so that they can potentially still be used to reproduce/diagnose the issue, and, in the case of app.settings, to restore any potential custom settings.

3

Howdy,
It immediately enters the error state.
Thanks for the suggestions and quick response. the jitcache, and globalcache didn’t have any effect. However, removing the app.settings then reloading the libraries has allow access to the program. Furthermore, It recognized those problematic photos.

Prior to deleting the settings, I wasn’t able to access the program at all. Thankfully, after deleting the settings, a crash error dialog still popped up, so I was able to send a crash report. I’ve attached a screen shot of what I was seeing, and sent my settings file to the bugs email.

Screenshot 2025-06-19 093835
Screenshot 2025-06-19 0938352433×1285 80.1 KB

Let me know if there’s anything further I can do to help.

4

Thanks for the follow-up! I was able to reproduce the issue by using the same app.settings. The issue is a combination of two factors:

  1. The window position that was saved for the window is negative, so that the window is completely above the upper edge of the screen
  2. A modal dialog is opened directly at startup, which makes it impossible to close/move/maximize the main window through the task bar

In my case, after pressing escape, it became possible to right-click the window-thumbnail and choose “Move” to move it back into the visible area.

So, apparently we need to add a logic that moves the window into a visible area of the desktop at startup.

Just for a better understanding of the cause, do you potentially have a setup, where you sometimes use multiple monitors and sometimes not?

5

Implemented this now for the next release tomorrow. This indeed fixes the issue.

6

Yes, I do have a setup when I sometimes use dual monitors and sometimes do not. My computer is a 2-1, and I have another monitor that connects when I dock my computer, so I have 3 different configurations because windows automatically changes the aspect ratio when I flip it to tablet mode.
That’s helpful to know. I didn’t even think about the window being set to negative coordinates.

7

Okay, that’s good to know. I have a Thinkpad Yoga that I can use to see if I can find any other issues. The just released 1.0.0-rc.22 now ensures that the window will be fully visible on the screen closest to its stored position, but maybe there is also a way to mess up the window position while it’s still running.

1 Like