# Crash using Find starting from a Localized Path
**URL:** https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148
**Category:** Help & Support
**Created:** [June 16, 2018, 8:15am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148 "2018-06-16T08:15:12Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 16, 2018, 8:15am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/1 "2018-06-16T08:15:12Z")
thanks for the 12.9.1 update to fix this issue ( [Dopus 12.8.1 vertical bar support for wsl is not working/dopus crashes while encountring wsl softlink during find](https://resource.dopus.com/t/dopus-12-8-1-vertical-bar-support-for-wsl-is-not-working-dopus-crashes-while-encountring-wsl-softlink-during-find/28925) ), but it has led to serious application crash.
go to a directory which has many soft/symbolic links of wsl
open the find tab and start searching such that the you will have the results
this triggers the application crash.
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 16, 2018, 9:01am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/2 "2018-06-16T09:01:12Z")
If any crash dumps were generated, please send them to us so we can investigate:
> [@Automatic crash logs (for bug reports)](https://resource.dopus.com/t/crash-dumps-for-bug-reports/8861):
>
> In the event of a crash, Directory Opus usually creates a log file (also known as a "dump file") with information that may be useful in diagnosing the problem. (For problems which don't result in a crash -- e.g. freezes or abnormal CPU usage -- you …
If you go back to 12.9 does the problem go away? I can't think of any changes in 12.9.1 which would start to cause that problem.
It's possible the crash is not in Opus and is a shell extension something else has installed going wrong, but we can usually use the crash dumps to see if that's the case.
If there are no crash dumps, this guide has other suggestions on tracking down the cause of this type of crash:
> [@Crash, exit or high CPU when viewing certain directories](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-viewing-certain-directories/1325/1):
>
> See also: [Crash, exit or high CPU usage when right-clicking certain files](https://resource.dopus.com/t/crash-exit-or-high-cpu-when-right-clicking-certain-files/1335)[How to find components causing high CPU usage](https://resource.dopus.com/t/how-to-find-components-causing-high-cpu-usage/14144)[How to find components causing memory leaks](https://resource.dopus.com/t/how-to-find-components-causing-memory-leaks/10135)[Crash dumps for bug reports](https://resource.dopus.com/t/crash-dumps-for-bug-reports/8861)[General slowdown or instability investigation steps](https://resource.dopus.com/t/general-slowdown-or-instability-investigation-steps/4618)Summ…
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 16, 2018, 2:51pm UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/3 "2018-06-16T14:51:17Z")
I tried in version 12.9 still its crashing. I don't see any log being generated, but I see a dialog box.
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 16, 2018, 3:25pm UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/4 "2018-06-16T15:25:50Z")
If you see that then a crash dump should be generated. Did you look in the folder the guide says to look in?
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 17, 2018, 8:50am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/5 "2018-06-17T08:50:43Z")
sorry there were no dumps or logs in the folder for which find generated crash.
but I could narrow down the trigger for this crash, if the current folder is having wsl symbolic links and the filter condition should match the symbolic links name.
see the above sample test folder, search for 'kernels' in C:\Users\karthikeyan\prj\tstfilter\a\softlnk -\> crash happens
searching for 'kernels' in C:\Users\karthikeyan\prj\tstfilter\a -\> does not crash
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 17, 2018, 9:11am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/6 "2018-06-17T09:11:06Z")
Is there anything different about WSL symbolic links compared to normal ones in Windows created without WSL?
What do the Type and Target columns (both under the General category) show for those links?
Could you list the steps to re-create what you have? e.g. WSL commands used to create the links.
Are those links on your C drive, presumably normal NTFS, or is there a junction or similar involved and the folder in question is on another drive/filesystem?
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 17, 2018, 9:25am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/7 "2018-06-17T09:25:45Z")
And just to confirm, you've looked in `%TEMP%\DOpus.Minidumps` (e.g. `C:\Users\\AppData\Local\Temp\DOpus.Minidumps` for the crash dumps? They'll only be found there.
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 18, 2018, 5:38am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/8 "2018-06-18T05:38:32Z")
Let me check the directory and upload if i have any dumps.
I used "ln -s" to create symbolic links in wsl. I am running Ubuntu 16.04 on wsl and my disk is ntfs formated. If you want i can upload the directory content as tar gzip.
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 19, 2018, 3:37am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/9 "2018-06-19T03:37:51Z")
> [@karthikeyan\_sw](#):
>
> hope the enclosed dump helps you to debug.
[dopus.20180618.002852.zip](https://resource.dopus.com/uploads/default/original/3X/1/b/1bf1e34a7c2f96e36be8b95320be82f869908690.zip) (27.3 KB)
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 19, 2018, 3:41am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/10 "2018-06-19T03:41:30Z")
[tstfilter.tgz](https://resource.dopus.com/uploads/default/original/3X/7/a/7a84360ba7a133196c3c7313bb7679b1f5f96e43.tgz) (457 Bytes)
this is the sample directory which triggers the crash during find operation.
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 19, 2018, 7:20am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/11 "2018-06-19T07:20:43Z")
Many thanks for the crash dump!
If you turn off **Preferences / Folders / Folder Display / Display localized folder names** , do you still see the same problem?
If you no longer get the crash when that is turned off, we've found and fixed the problem. But if you still get the crash, please let us know so we know to look for something extra.
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 20, 2018, 2:49am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/12 "2018-06-20T02:49:30Z")
I have a desktop with amd cpu, and its not crashing there even before trying your suggestion.
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 20, 2018, 3:00am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/13 "2018-06-20T03:00:35Z")
> [@Leo](#):
>
> crash, please let us know so we know to look for something extra.
The crash doesn't look like it has any connection to WSL symbolic links. It definitely won't be related to AMD CPUs either.
We think it might be tied to folders that have localised names, and setting up the Find so it starts in the path which uses the localised name rather than the physical path.
On the machine that was seeing the crash before, please check that the crash still happens with things as they are, and then that it no longer happens when the **Display localized folder names** option is turned off.
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 20, 2018, 3:36am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/14 "2018-06-20T03:36:57Z")
> [@Leo](#):
>
> On the machine that was seeing the crash before, please check that the crash still happens with things as they are, and then that it no longer happens when the **Display localized folder names** option is turned off.
in my amd desktop Display localized folder names is enabled, but still no crash
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 20, 2018, 3:54am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/15 "2018-06-20T03:54:10Z")
my folder has special character _\*_ (a\*)
invoking search pattern _kerne\*_ under a\* displays all 6 files
but invoking same seach pattern under the _softlink_ displays empty results even though 3 files matches. repeated invoking by pressing multiple enter key triggers the crash dialog. it happens even in my amd desktop
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 20, 2018, 3:56am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/16 "2018-06-20T03:56:30Z")
turning off display localized folder names fixes the crash but the find result window is still empty. so I guess it needs a proper fix.
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 20, 2018, 4:22am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/17 "2018-06-20T04:22:55Z")
That's expected. That is not the folder's real path by the look of things (you can't use a `*` in a filepath in windows, although I'm not sure it is really a \*, it looks like a raised dot in some places in your screenshots), so if you specify that as the Find In path, it has to be translated into the real path, which is where the crash was happening. (If the translation is not done, i.e. when the option is turned off, then it won't find anything because the path you're specifying does not really exist, at least not on the Windows side of things. Only the translated path exists.)
In that case it will all be fixed in the next update.
I'll rename the thread to match what the issue is about.
---
### Author:  [@karthikeyan\_sw](https://resource.dopus.com/u/karthikeyan_sw)
#### Post date: [June 20, 2018, 4:52am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/18 "2018-06-20T04:52:13Z")
in wsl its a _\*_ , by the way search works if you are right under the folder which has _\*_ , in my case _a\*_. but it fails only if you go to the folder that has soft links to its parent
a\*\softlink\kernel-01.cpp -\> a\*\kernels-01.cpp
---
### Author:  [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [June 20, 2018, 7:24am UTC](https://resource.dopus.com/t/crash-using-find-starting-from-a-localized-path/29148/19 "2018-06-20T07:24:29Z")
The softlinks were not even being looked at at the stage the crash happened, for what it's worth.
I'd recommend not using \* in any paths. It's a bit ridiculous that WSL even allows that to happen on an NTFS volume.