Known problems or limitations
Error: JSplitter v3.7.6 ({86BB0E71-DE6C-4480-BFA5-673B29F223E1}: XXX)
Out of memory: 1332/1073741824 bytes
On some setups after loading a script or while running, specially with large libraries (> 100K tracks), it may be possible that the JS host crashes with an Out of Memory error (like the one above). Unfortunately that's a components limitation, in particular in x86 setups, since it can not have access to the required amount of RAM for processing. There are multiple possibilities.
- Avoid using Album Art display, since it will require more memory than displaying the list as a tree.
- Simplify TF patterns or apply filters to views.
- Use x64 foobar2000 along x64 components. Check if your preferred JS host provides a x64 version.
- Setting a higher RAM limit at the JS host. Input the highest number you can at the following setting (both SMP and JSplitter offer similar options):
After loading a script into a panel, the panel may crash if foobar does not has the required [full] access to the folder where the scripts reside. This may happen in portable installations since Win 11 restrict permissions to folders outside 'Program Files' or 'Users'. Ask at foobar forums for support.
The error will warn about script files not being found, although they are in place. This is due to incorrect relative path handling on some systems. In such case, take a look at the ’_switchPaths.zip’, decompress it and follow its instructions. Scripts will be automatically edited to use absolute paths at script loading, thus fixing the problem. The cmd file (.bat) will have to be rerun on future playlist manager updates. Obviously this is only a workaround and a proper fix is expected on posterior SMP releases.
This is not an script error but an SMP feature to avoid scripts blocking the entire software (please don't report it). It's common for processor intensive tasks which require more time to finish (just press continue). Clicking 'stop the script' will crash the panel.
Since some operations may need more time than usual, to avoid seeing the popup, it’s recommended to change the timer at configuration to the highest value allowed. NOTE: JSplitter allows to set it to 0 to disable it.
