Hi,
New user, tester.. I’ve tried to add my folder which includes 250k+ photos.
I did expect it to take along time.. but it I’m missing an indication how many photos of total have been prosessed ? (as I dont understand how long its going to be running for..)
Its using all bandwith, and I mean all.. thats impressive 
.
Looks very good this, but i’m eager to look at this when my photos have loaded.
Is there any indication, or a way to tell it to only scan some of the photos, other than selecting a nested folder with a few images ?
Still runnning… and eating up memory. So I stop the application and start it again.
Its using small amount of cpu, memory is going up slowly, and the bandwitdh max out when it needs to and goes down again to normal. I still wonder how many files is has left to count…
Hi,
currently the only way to exclude certain folders is indeed to deselect the parent folder and then only select the sibling folders instead. There was a request to add the possibility to exclude certain folders and we will probably add that soon(ish), even though this doesn’t have a concrete schedule, yet.
Just to clarify what part of the process you are stuck in, what does the entry in the “Notification Center” in the lower right of the application window say when you open up the panel?
Another question, what is the total size of the folder and what kind of drive are they being stored on? I personally have an external SMR-style hard disk and that tends to be very slow. However, even at that speed it should only take hours, not days, so there must be something else going on.
Hi, thank you for good answers.
Its just alot of data
I’m currently scanning my whole dataset. (masterfolder + underlying folders)
The program crashes after several 10+ hours running, so I just have to start it up again. Its okay - but an autorestart when reading folders would be nice. Although it should not crash, understand that.
Click send report fails. And uploading the aspect-log-crash-20260204T235951.sdl is about 150mb. each.. Kinda want to know whats in there aswell before sending so a transparent view of error would be my suggestion.
At this point counted up 244.141 photos..but it keeps going…
I see this on top under “photo stream”.
Down to the right i see “syncronizing file system…”
System is NAS with 8 disks, 2xRaidz1 (2x4disks). Should be plenty of speed
Also I have turned off antivirus for that drive and the speed i 300% faster…
I Just would like a counter how much is left, and looking forward to trying this program.
(I need to see that it can handle large amount of photos)
The applications crashes (restartet now 10+), is there a log output I could follow to see which file or what happens when it failes so I can help find the problem.
Seems like it does not count any more files.. and loops.. the image on top which displays number of photos does not change anymore..
..having said this I’m still looking forward to trying out this software
In the aspect-log.sdl log file, you could look at the last few lines to see whether there is a line with something like “An unrecoverable … error has been encountered”. If there is, the following lines should contain a call stack that ideally pinpoints the error. Otherwise, if you are on macOS, the system crash report usually contains useful information.
If none of these apply, we might have to try to get more information using a debugger (WinDbg on Windows or gdb/lldb on Linux).
By the way, when the crash report dialog comes up, does it say anything about the crash possibly being caused by certain image files?
1 Like
Ah this is very useful, thank you.
I see now the program scans the whole system again for changes..250k files takes time to go through 
I will follow the log and see what happens next when/if it stops again..
I’m using Windows 11.
The crash report indicates a file, and I will check this more now.. It pointed to a “normal .png file”.
I will post again.
This is what is startet to say when it stopped and the application closed.
First line is okey, then it start to have errors.
line "Change #126028 detected: (addFile: const(AddFileAction)(file:///Z:/MyPictures/Google%20Photos/Photos%20from%202019/snapshot(7042)%20-%202021-04-04%20-%2009-10-04%20-%201280x720.jpg, (shoeBoxFolder: shoeBoxFolder(1:2:0)), [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], [89, 128, 184, 160, 243, 75, 91, 19, 6, 248, 224, 123, 68, 94, 216, 16], 106821)) (URL: file:///Z:/MyPictures/Google%20Photos/Photos%20from%202019/snapshot(7042)%20-%202021-04-04%20-%2009-10-04%20-%201280x720.jpg, library at file:///Z:/Henning%E2%80%99s%20Aspect%20Library)" level="diagnostic" time=2026/02/07 19:41:37.4551519-UTC file="changedetector.d" line=747 thread="Main" threadID=2938547215 fiberID=2557169203;
line "" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=129 thread="Main" threadID=2938547215 fiberID=0;
line "An unrecoverable logic error was encountered: Colon in path that is not part of a drive name." level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=130 thread="Main" threadID=2938547215 fiberID=0;
line " File: C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.3\\vibe-core\\source\\vibe\\core\\path.d" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=133 thread="Main" threadID=2938547215 fiberID=0;
line " Line: 505" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=134 thread="Main" threadID=2938547215 fiberID=0;
line " Callstack:" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7AD60D705 in krtek.core.process.printFatalError!true at C:\\Users\\Build\\dev\\krtek\\core\\krtek\\core\\process.d(139)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7AD60D3DD in krtek.core.process.setupErrorHandling.__lambda_L35_C18(__T2, __T3, __T4)(f, l, m) at C:\\Users\\Build\\dev\\krtek\\core\\krtek\\core\\process.d(35)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADAFF6A8 in d_assert_msg" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ACAED21F in vibe.core.path.GenericPath!(WindowsPathFormat).fromTrustedString at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.3\\vibe-core\\source\\vibe\\core\\path.d(505)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADA64F13 in vibe.core.file.DirectoryWatcher.Context.onChange at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.3\\vibe-core\\source\\vibe\\core\\file.d(899)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADAA076C in eventcore.drivers.winapi.watchers.WinAPIEventDriverWatchers.onIOCompleted at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\watchers.d(197)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADA9B4A0 in eventcore.drivers.winapi.core.WinAPIEventDriverCore.doProcessEvents at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\core.d(207)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADA9B36C in eventcore.drivers.winapi.core.WinAPIEventDriverCore.processEvents at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\core.d(118)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADA6CEEE in vibe.core.task.TaskScheduler.process at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.3\\vibe-core\\source\\vibe\\core\\task.d(938)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADA6D19D in vibe.core.task.TaskScheduler.waitAndProcess at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.3\\vibe-core\\source\\vibe\\core\\task.d(1008)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADA55C47 in vibe.core.core.runEventLoop at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.3\\vibe-core\\source\\vibe\\core\\core.d(219)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7AD80F8A0 in inbase.gui.drivers.win32.Win32UIDriver.run at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\inbase\\0.37.31\\inbase\\gui\\inbase\\gui\\drivers\\win32.d(197)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7AD7E0159 in inbase.gui.application.runApplication at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\inbase\\0.37.31\\inbase\\gui\\inbase\\gui\\application.d(79)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7AC7D1AB9 in main.appMain at C:\\Users\\Build\\dev\\krtek\\app-desktop\\source\\main.d(209)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADB02881 in void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).runAll()" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADB0252B in d_run_main2" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7ADB027E6 in d_wrun_main" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF7AE18B90C in __scrt_common_main_seh at D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl(288)" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF95CB9E8D7 in BaseThreadInitThunk" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "0x00007FF95EC4C53C in RtlUserThreadStart" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
line "" level="fatal" time=2026/02/07 19:41:37.5126592-UTC file="process.d" line=140 thread="Main" threadID=2938547215 fiberID=0;
Okay, I’ve seen the same issue in a crash report recently, but haven’t been able to pinpoint where the invalid path comes from. To hopefully get to the root cause, I have prepared a build that also outputs the path corresponding to the error message (“Colon in path that is not part of a drive name.”): https://download.bildhuus.com/temp/aspect-1.0.0-rc.45-16-gbff0524eb-setup.exe
Can you try to re-run with this installed and then post the new error message?
1 Like
Thank you. Downloaded and trying to run it again. Looks similar. I’m happy to go again and find the root cause.
line "" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=129 thread="Main" threadID=3338724878 fiberID=0;
line "An unrecoverable logic error was encountered: Cannot append absolute path." level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=130 thread="Main" threadID=3338724878 fiberID=0;
line " File: C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.4\\vibe-core\\source\\vibe\\core\\path.d" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=133 thread="Main" threadID=3338724878 fiberID=0;
line " Line: 860" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=134 thread="Main" threadID=3338724878 fiberID=0;
line " Callstack:" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C53A3885 in krtek.core.process.printFatalError!true at C:\\Users\\Build\\develop\\krtek\\core\\krtek\\core\\process.d(139)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C53A355D in krtek.core.process.setupErrorHandling.__lambda_L35_C18(__T2, __T3, __T4)(f, l, m) at C:\\Users\\Build\\develop\\krtek\\core\\krtek\\core\\process.d(35)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C589CB88 in d_assert_msg" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C4562DB9 in vibe.core.path.GenericPath!(WindowsPathFormat).opBinary!\"~\" at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.4\\vibe-core\\source\\vibe\\core\\path.d(860)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C57FFDA6 in vibe.core.file.DirectoryWatcher.Context.onChange at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.4\\vibe-core\\source\\vibe\\core\\file.d(899)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C583B5EC in eventcore.drivers.winapi.watchers.WinAPIEventDriverWatchers.onIOCompleted at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\watchers.d(197)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C5836320 in eventcore.drivers.winapi.core.WinAPIEventDriverCore.doProcessEvents at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\core.d(207)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C58361EC in eventcore.drivers.winapi.core.WinAPIEventDriverCore.processEvents at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\core.d(118)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C5807FC7 in vibe.core.task.TaskScheduler.waitAndProcess at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.4\\vibe-core\\source\\vibe\\core\\task.d(993)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C57F0AC7 in vibe.core.core.runEventLoop at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\vibe-core\\2.13.4\\vibe-core\\source\\vibe\\core\\core.d(219)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C55AAD80 in inbase.gui.drivers.win32.Win32UIDriver.run at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\inbase\\0.38.1\\inbase\\gui\\inbase\\gui\\drivers\\win32.d(197)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C557ADF9 in inbase.gui.application.runApplication at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\inbase\\0.38.1\\inbase\\gui\\inbase\\gui\\application.d(79)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C4561AA9 in main.appMain at C:\\Users\\Build\\develop\\krtek\\app-desktop\\source\\main.d(209)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C589D701 in void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).runAll()" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C589D3AB in d_run_main2" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C589D666 in d_wrun_main" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF6C5F2678C in __scrt_common_main_seh at D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl(288)" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF95CB9E8D7 in BaseThreadInitThunk" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "0x00007FF95EC4C53C in RtlUserThreadStart" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
line "" level="fatal" time=2026/02/08 21:31:01.9883593-UTC file="process.d" line=140 thread="Main" threadID=3338724878 fiberID=0;
Interesting, now it’s a slightly different check that fails in almost the same place. Unfortunately that means, the additional info about the failing path isn’t included in the new error message. I’ve uploaded another build with additional diagnostic output: https://download.bildhuus.com/temp/aspect-1.0.0-rc.45-16-gbff0524eb-2-setup.exe
Hopefully it won’t trigger a third different check this time…
I’m not sure if this is different but hope this can tell you something..
I dont see any image wrongs/error above this code.
line "" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=129 thread="Main" threadID=4181980686 fiberID=0;
line "An unrecoverable logic error was encountered: Sub directory path should not be absolute: .::TMPNAME:D:6480%451058947078481638:" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=130 thread="Main" threadID=4181980686 fiberID=0;
line " File: C:\\Users\\Build\\develop\\vibe-core\\source\\vibe\\core\\file.d" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=133 thread="Main" threadID=4181980686 fiberID=0;
line " Line: 901" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=134 thread="Main" threadID=4181980686 fiberID=0;
line " Callstack:" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F77D38A5 in krtek.core.process.printFatalError!true at C:\\Users\\Build\\develop\\krtek\\core\\krtek\\core\\process.d(139)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F77D357D in krtek.core.process.setupErrorHandling.__lambda_L35_C18(__T2, __T3, __T4)(f, l, m) at C:\\Users\\Build\\develop\\krtek\\core\\krtek\\core\\process.d(35)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7CCCC68 in d_assert_msg" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7C2FEA5 in vibe.core.file.DirectoryWatcher.Context.onChange at C:\\Users\\Build\\develop\\vibe-core\\source\\vibe\\core\\file.d(903)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7C6B6CC in eventcore.drivers.winapi.watchers.WinAPIEventDriverWatchers.onIOCompleted at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\watchers.d(197)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7C66400 in eventcore.drivers.winapi.core.WinAPIEventDriverCore.doProcessEvents at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\core.d(207)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7C662CC in eventcore.drivers.winapi.core.WinAPIEventDriverCore.processEvents at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\eventcore\\0.9.38\\eventcore\\source\\eventcore\\drivers\\winapi\\core.d(118)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7C380A7 in vibe.core.task.TaskScheduler.waitAndProcess at C:\\Users\\Build\\develop\\vibe-core\\source\\vibe\\core\\task.d(993)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7C20AF7 in vibe.core.core.runEventLoop at C:\\Users\\Build\\develop\\vibe-core\\source\\vibe\\core\\core.d(219)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F79DADB0 in inbase.gui.drivers.win32.Win32UIDriver.run at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\inbase\\0.38.1\\inbase\\gui\\inbase\\gui\\drivers\\win32.d(197)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F79AAE29 in inbase.gui.application.runApplication at C:\\Users\\Build\\AppData\\Local\\dub\\packages\\inbase\\0.38.1\\inbase\\gui\\inbase\\gui\\application.d(79)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F6991AA9 in main.appMain at C:\\Users\\Build\\develop\\krtek\\app-desktop\\source\\main.d(209)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7CCD7E1 in void rt.dmain2._d_run_main2(char[][], ulong, extern (C) int function(char[][])*).runAll()" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7CCD48B in d_run_main2" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F7CCD746 in d_wrun_main" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FF6F835686C in __scrt_common_main_seh at D:\\a\\_work\\1\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl(288)" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FFD90DAE8D7 in BaseThreadInitThunk" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "0x00007FFD919CC53C in RtlUserThreadStart" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
line "" level="fatal" time=2026/02/11 10:18:24.3614795-UTC file="process.d" line=140 thread="Main" threadID=4181980686 fiberID=0;
It seems like maybe the NAS(?) on which the library is stored creates a temporary directory that has a name that is invalid on Windows (.::TMPNAME:D:6480%451058947078481638: in this case, colons are only allowed for drive letters and special device names). We are then making the wrong assumption that all file names reported by Windows are actually valid, which then causes a logic check to fail.
I managed to configure our SAMBA server to keep such filenames and was able to reproduce the error by creating a similar folder name from Linux. This should be fixed in the next update which will be released ASAP.
1 Like
Trying: aspect-1.0.0-rc.46-setup.exe
Update: I think this got past the error now. Down to on the right corner its saying:
Synchronizing File System…
Applying file system changes to the library…
And I now staring to see pictures on the screen..
…but still working..