Skip to content

Commit fb82643

Browse files
committed
Fix file location
1 parent eb9dfb4 commit fb82643

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed

docs/preview/troubleshooting/crashes.md renamed to docs/preview/guides/troubleshooting/crashes.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ There are a few major types of crashes:
3030

3131
* **Out of memory errors**: A DuckDB crash can also be a symptom of the operating system killing the process.
3232
For example, many Linux distributions run an [OOM reaper or OOM killer process](https://learn.redhat.com/t5/Platform-Linux/Out-of-Memory-Killer/td-p/48828), which kills processes to free up their memory and thus prevents the operating system from running out of memory.
33-
If your DuckDB session is killed by the OOM reaper, consult the [“OOM errors” page]({% link docs/preview/troubleshooting/oom_errors.md %})
33+
If your DuckDB session is killed by the OOM reaper, consult the [“OOM errors” page]({% link docs/preview/guides/troubleshooting/oom_errors.md %})
3434

3535
## Recovering Data
3636

0 commit comments

Comments
 (0)