Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Strange unceasing crash occurring constantly within last few days. (Read 3908 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #25 –
I forgot to mention that after rebuilding the Media Library, save it by pressing Shift key + foobar menu > File > Save configuration.

\profile\library-v2.0
\profile\playlists-v2.0
\profile\metadb.sqlite

Do not move the folders and files you moved to the desktop back.
Even if it's a hassle, please create a new Playlist. If you have a lot of Auto Playlists, it will take a long time to load them.
-----
Can you tell me the specs of your machine?
Is it homemade?

CPU: 13th Gen Intel(R) Core(TM) i9-13900K
RAM GB:
graphic:

As I mentioned before, the loading speed of the built-in storage is much faster. Please consider it.
I feel it would be a waste to use a portable HDD with that CPU. I think you'll feel the difference even more.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: Strange unceasing crash occurring constantly within last few days.

Reply #26 –
I spoke too soon. After foobar had finished rebuilding the library I played a track from an album and a few moments later it had crashed again. Pretty stumped at this point. I didn't restore the files that I moved to the desktop.

Attached are my specs. My GPU is an RTX 3090.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #27 –
Thsnks.
Could the Spider Monkey Panel be the cause of the crash when playing?
Please back up the Georgia Reborn folder.

Actually, I'd like to know the track information that's being played.
Is it a specific file type that's crashing?
for example: CUE (FLAC)
What happens if you play several mp3 albums in a row?

Why not start from scratch with the portable version?
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: Strange unceasing crash occurring constantly within last few days.

Reply #28 –
Quote from: Air KEN on
Thsnks.
Could the Spider Monkey Panel be the cause of the crash when playing?
Please back up the Georgia Reborn folder.

Actually, I'd like to know the track information that's being played.
Is it a specific file type that's crashing?
for example: CUE (FLAC)
What happens if you play several mp3 albums in a row?

Why not start from scratch with the portable version?

I want to say that SMP is probably the reason, but I wanna know why it started happening only recently. I installed foobar along with the og georgia theme the same day I built the rig and it was running fine for years. I'd prefer to keep the theme purely for aesthetic reasons and the fact it had everything conveniently located. I don't know whether or not other themes all use SMP which means I might have the same crash re-occur even if I change to a different theme. Already getting the same crash with georgia reborn.

Almost all of my library are FLAC files, save for some obscure mixtapes that were made with lossy samples to begin with but the crash has always happened while I'm playing FLAC files. As of right now, I can't get play more than 1 or 2 tracks before foobar crashes.

For now I'll be using a clean portable instance until the m.2 arrives so I can troubleshoot whether or not having the library on an SSD makes a difference.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #29 –
I am waiting for the results.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: Strange unceasing crash occurring constantly within last few days.

Reply #30 –
Note that having media library on faster media can make the initial library scan faster and can speed up various maintenance tasks, like making a backup of the library as reading the bytes is faster. But it offers no benefits for foobar2000 otherwise. Only thing that matters to foobar2000 is that its own database is located on a fast media.

Quote from: thisisbleak on
I monitored the memory usage via task manager while playing a song and it went up to 158MB before it crashed. As for library size; it's over 2TB.
Library size is irrelevant, number of tracks and how much metadata you have can be.
That memory usage doesn't sound correct. Can you do it again using the Details view of Task Manager and check also the Commit value.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #31 –
Quote
Library size is irrelevant, number of tracks and how much metadata you have can be.
That memory usage doesn't sound correct. Can you do it again using the Details view of Task Manager and check also the Commit value.
Uhm... well even if I get your point it's a bit misleading. Metadata needs disk space xd i.e. a 8TB library will probably have more metadata than a 2TB library for regular users in 99% use cases. Obviously you may argue you can have 10000 mp3 files with 100MB lyrics or have 10^9 mp3 files with no tags at all, thus the first one requiring more memory. But that's not an usual thing, and for most people more metadata = bigger libraries.

Anyway unless this user has an exotic library, no one has had any problem with those sizes. People is complaining having 10 times more than that.

I'm not really understanding the testing though. It is not clear if all installations tested use SMP or not. It's stated that multiple themes were tested (?) but the idea is to test a clean portable install, not themes which introduce more variables.

Quote
...but the crash has always happened while I'm playing FLAC files. As of right now, I can't get play more than 1 or 2 tracks before foobar crashes.
Also things magically crashing for no reason without any change usually point to disk corruption or CPU/RAM problems.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #32 –
The topic starter has already stated twice that there is no crashing with a clean portable version. The first time right above your first post.

I doubt there haven't been changes. I'd assume his library is constantly growing with new files. Components get updates and their memory footprints change. OS and drivers get updates. All affect in the very least the memory usage, if nothing else.

Also Spider Monkey Panel is currently the 16th crashiest component from directly blamable components.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #33 –
Quote from: regor on
Quote
Library size is irrelevant, number of tracks and how much metadata you have can be.
That memory usage doesn't sound correct. Can you do it again using the Details view of Task Manager and check also the Commit value.
Uhm... well even if I get your point it's a bit misleading. Metadata needs disk space xd i.e. a 8TB library will probably have more metadata than a 2TB library for regular users in 99% use cases. Obviously you may argue you can have 10000 mp3 files with 100MB lyrics or have 10^9 mp3 files with no tags at all, thus the first one requiring more memory. But that's not an usual thing, and for most people more metadata = bigger libraries.

Anyway unless this user has an exotic library, no one has had any problem with those sizes. People is complaining having 10 times more than that.

I'm not really understanding the testing though. It is not clear if all installations tested use SMP or not. It's stated that multiple themes were tested (?) but the idea is to test a clean portable install, not themes which introduce more variables.

Quote
...but the crash has always happened while I'm playing FLAC files. As of right now, I can't get play more than 1 or 2 tracks before foobar crashes.
Also things magically crashing for no reason without any change usually point to disk corruption or CPU/RAM problems.

Would it be a good suggestion to run mem86 to check for faulty RAM? Foobar running either of those two themes seem to be the only program I've encountered instability with. Disk Management shows my F: drive as healthy (I don't know how reliable that is, though.) I've tested 3 instances thus far. My original foobar that has had the Original Georgia theme installed on it since the same day I built the PC. Had worked seamlessly for 2 years before it just started having problems a few days ago. I should note my music library has obviously grown exponentially over the course of the rig's lifetime. The other instances are another portable 32bit installation with the Georgia ReBorn theme in order to test whether or not another theme would have stopped the crashing, but unfortunately with this instance SMP crashes on startup or foobar crashes while building the library. The third instance is another portable instance with no custom themes or addons installed. It has yet to crash and has built the media library without crashes and hasn't crashed during the day with regular usage (playing music; am able to play full albums back-to-back without problems.)                                                                                                   

Re: Strange unceasing crash occurring constantly within last few days.

Reply #34 –
Not really sure what's your point about SMP though. JS components are the most complex ones (since you can do essentially anything), so obviously it's natural that they have crashes. Some of those crashes come from people hitting RAM limits being for years using 32 bits and most other SMP crashes on latest months come from people using an outdated script and not applying the fix. Yep, the latter should be solved by SMP itself.

We have components like this broken since a decade and still not listed as "problematic". So.. your numbers only tell me that Biography script is precisely one of the most popular things being used by people. No wonder why.

Quote
I want to say that SMP is probably the reason, but I wanna know why it started happening only recently
Just saying SMP is the problem does not answer why things worked fine and some day they don't.

For ex. the user could just test a clean install with SMP and NOT install any theme. I doubt that will crash anything. If crashes happen when using specific themes, then problem is related to such specific themes. For ex. I know you can crash foobar if you pass wrong image objects via SMP, but that clearly points to a problem in your script or files.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #35 –
Quote
The other instances are another portable 32bit installation with the Georgia ReBorn theme in order to test whether or not another theme would have stopped the crashing, but unfortunately with this instance SMP crashes on startup or foobar crashes while building the library.
Report that crash at Georgia thread since it clearly points to some problem parsing specific track files which could be solved.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #36 –
Scripts are not to blame for any component crash ever. All component crashes are component bugs, It really is that simple.

The worst thing a bad script should ever do is throw a relatively harmless script error.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #37 –
Quote from: Case on
Note that having media library on faster media can make the initial library scan faster and can speed up various maintenance tasks, like making a backup of the library as reading the bytes is faster. But it offers no benefits for foobar2000 otherwise. Only thing that matters to foobar2000 is that its own database is located on a fast media.

Quote from: thisisbleak on
I monitored the memory usage via task manager while playing a song and it went up to 158MB before it crashed. As for library size; it's over 2TB.
Library size is irrelevant, number of tracks and how much metadata you have can be.
That memory usage doesn't sound correct. Can you do it again using the Details view of Task Manager and check also the Commit value.

Played a FLAC file on the original instance with Georgia theme installed and monitored via task manager. Memory usage went up to
428,300K before SpiderMonkeyPanel crashed with this error 

Re: Strange unceasing crash occurring constantly within last few days.

Reply #38 –
Quote
Scripts are not to blame for any component crash ever. All component crashes are component bugs, It really is that simple.
No one said otherwise, but you can avoid such crash xd as shown on the biography script. Anyway it brings nothing useful to discuss that, SMP is not being actively developed, so either we find the root of the problem and avoid it or there is nothing to do.

Quote
The worst thing a bad script should ever do is throw a relatively harmless script error.
In an ideal world with basic scripts.

I find pretty innocent to expect a component with full system access and RAM limits imposed by the parent to not crash foobar. Heck even win 11 added bugs to SMP reading packages some updates ago. xd

Re: Strange unceasing crash occurring constantly within last few days.

Reply #39 –
Quote from: thisisbleak on
Original instance with Georgia theme installed and monitored via task manager. Memory usage went up to
428,300K before SpiderMonkeyPanel crashed with this error 
You are not reporting the right memoy usage. Please post screenshots. We need commit size.

And obviously if foobar is using more RAM than allowed on 32 bits, it will crash. Adding SMP + Georgia on top of that just increases RAM requirements.

EDIT: Also... is that the old Georgia theme? That's not Georgia Reborn.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #40 –
Quote from: regor on
Quote from: thisisbleak on
Original instance with Georgia theme installed and monitored via task manager. Memory usage went up to
428,300K before SpiderMonkeyPanel crashed with this error 
You are not reporting the right memoy usage. Please post screenshots. We need commit size.

And obviously if foobar is using more RAM than allowed on 32 bits, it will crash. Adding SMP + Georgia on top of that just increases RAM requirements.

EDIT: Also... is that the old Georgia theme? That's not Georgia Reborn.
Yes that's the instance running old georgia theme. First time I'm getting the red SMP error crash on that instance. And sorry for not giving enough info, is this screenshot better? This is while playing a FLAC.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #41 –
You need the memory usage when it crashes. It makes zero sense that it uses 500MB and then randomly crash due to RAM limits (+2gb?) unless the script is doing something weird.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #42 –
Quote from: Case on
Note that having media library on faster media can make the initial library scan faster and can speed up various maintenance tasks, like making a backup of the library as reading the bytes is faster. But it offers no benefits for foobar2000 otherwise. Only thing that matters to foobar2000 is that its own database is located on a fast media.

I'm just saying that you should avoid portable hard drives.
This advice is based on my experience and that of others.
The HDD may not be recognized properly, may suddenly stop being recognized, or loading may be slow.
These can be quite stressful.
If you have an environment where you can add built-in storage, it will simply be convenient. I don't particularly care about M.2 SSD. Built-in HDD is fine too.
Internal M.2 SSDs have become commonplace in recent times.
This is common knowledge for people who build their own PCs.
I am not saying that you have to do it.

> But it offers no benefits for foobar2000 otherwise.
> Only thing that matters to foobar2000 is that its own database is located on a fast media.

Isn't that the biggest advantage?

> Note that having media library on faster media can make the initial library scan faster and can speed up various maintenance tasks, like making a backup of the library as reading the bytes is faster. But it offers no benefits for foobar2000 otherwise. Only thing that matters to foobar2000 is that its own database is located on a fast media

It's surprising to hear something like that in this day and age.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: Strange unceasing crash occurring constantly within last few days.

Reply #43 –
Quote from: regor on
You need the memory usage when it crashes. It makes zero sense that it uses 500MB and then randomly crash due to RAM limits (+2gb?) unless the script is doing something weird.

Was trying to recreate the crash earlier today before work but foobar decided to run crash-free that time lol. Was only about 10 minutes though before I left. Will try again later today when I get home. Is there anyway to reconfigure either the georgia or georgia reborn theme to run on jsplitter instead of SMP? I have limited knowledge on everything but from what I understand SMP is limited to 32bit architecture while jsplitter can be configured on 64bit instances and is similar to SMP? Do correct me if I'm wrong though. Just trying to troubleshoot all options.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #44 –
Quote from: regor on
You need the memory usage when it crashes. It makes zero sense that it uses 500MB and then randomly crash due to RAM limits (+2gb?) unless the script is doing something weird.

Was able to recreate the crash. Happened a few seconds after playing a song. Included screen and crash log.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #45 –
Yeah, you don't have too much metadata for the program to run out of memory. The crashes are simply caused by SMP having serious unfixed bugs.

Edit: Sorry, brain fart made me say "JSP" instead of "SMP" initially. The marc2k3's JScript panel is not crashy.
 

Re: Strange unceasing crash occurring constantly within last few days.

Reply #46 –
Quote from: Case on
Yeah, you don't have too much metadata for the program to run out of memory. The crashes are simply caused by SMP having serious unfixed bugs.

Edit: Sorry, brain fart made me say "JSP" instead of "SMP" initially. The marc2k3's JScript panel is not crashy.
Sucks because I really like both the Georgia and Georgia reborn themes. Any alternatives to SMP?

Re: Strange unceasing crash occurring constantly within last few days.

Reply #47 –
I have been using SMP for years and had not a single foobar crash unless I did something wrong (or RAM limits). But to each their own. (not denying it has bugs anyway). I can make JSP or even the whole windows crash anyday with any JS component on purpose though.

You will not find a modern theme on anything but SMP for practical reasons. JSP is based on old JS implementation which is a pain to code for (or simply impossible), unless you limit yourself to basic things. You have multiple UI-related single panels at JSP which I think may be good enough for most people though.

I already instructed a dozen of times to report your problems at Georgia thread. So make your choice.

Re: Strange unceasing crash occurring constantly within last few days.

Reply #48 –
Quote from: regor on
I have been using SMP for years and had not a single foobar crash

How utterly useless and irrelevant. The crash reports posted are being posted by the OP, not you. To put it bluntly, this is none of your business.

Quote
not denying it has bugs anyway

Yes you are. Repeatedly.


Re: Strange unceasing crash occurring constantly within last few days.

Reply #49 –
https://github.com/TheQwertiest/foo_spider_monkey_panel/issues
Count how many issues have been opened by me. xd

Oh wait, a bio workaround for a SMP bug... (if I denied it, then I would not post a workaround xd)
https://hydrogenaud.io/index.php/topic,112914.msg1051980.html#msg1051980

To put it bluntly, learn to read.