Thumbnail generation does not start on my external drive.
Check for other issues
- [X] I've checked for other issues, and none exist.
Issue description
It only generates the thumbnails when I open up the folders and subfolders manually.
Steps to reproduce
No response
Platform and versions
- OS:
- Spacedrive:
Development tool versions (optional)
Stack trace
No response
Additional context
No response
Code of Conduct
- [X] I agree to follow the Code of Conduct.
Are you exploring your folders through ephemeral indexer, or you added your external drive as a location?
I added the drive as location.
I'm on mac os 14.7 btw.
Hmm, the media processor job ran without issues? Because when we add a location, we dispatch a job that fetches all your files and generate thumbnails for them eagerly.
Chiming in, I have this issue with external drives on Mac with 0.4.2. The thumbnail job instantly gets canceled every time without fail only on external drives.
For me, the error is "too many files" which is a MacOS specific issue, if you run the command ulimit -n 10240 in the Terminal app this issue will miraculously go away. It is a hotfix and we will figure something out soon.
Source: https://discussions.apple.com/thread/251000125?sortBy=rank
Yes, it's not the first time that it happened. On another harddrive the thumbnails just appeared after a few days or so. The indexing went fine. But even the media view stays empty if I don't open a folder.Am 10.10.2024 22:22 schrieb fogodev @.***>: Hmm, the media processor job ran without issues? Because when we add a location, we dispatch a job that fetches all your files and generate thumbnails for them eagerly.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
will try it out tomorrow, thanks!Am 10.10.2024 22:41 schrieb Jamie Pine @.***>: Chiming in, I have this issue with external drives on Mac with 0.4.2. The thumbnail job instantly gets canceled every time without fail only on external drives. For me, the error is "too many files" which is a MacOS specific issue, if you run the command ulimit -n 10240 in the Terminal app this issue will miraculously go away. It is a hotfix and we will figure something out soon.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Closing due to v2 rewrite. If you encounter this issue in v2, please open a new issue.