Quote:
Yada yada. Beware of backfire...

Quote:

Mind sharing the playlist somewhere? The explosion you have is either:
- a MP3 making demuxer/decoder exploding
- some content in the playlist is incorrecly parsed by Jukebox

In both case, there should be no crash. Provide playlist for a start. And find the potential MP3 doing nasty things inside decoder/demuxer. Dichotomic algorithm is probably the way to go. Divide the playlist in two parts, load parts. If it breaks again, divide the offending playlist in two, repeat until you have a handful of MP3 in. Should be pretty quick to pinpoint the MP3 triggering doomday.

@ Tcheko - I have basically got the same advice from jacadcaps as to me checking through the files to establish where the error is.

Jacek is assisting me with identifying where this "bug" is - which does indeed totally "freeze" my system within about 5-8 seconds of starting to load the MP3 files even if I load it via the MorphOSBoot CD (which cannot be any more "vanilla" if I tried) running them in the latest version of Jukebox in v3.20 with the MP3 files I have always referred to in this thread.

These files run without issue in Jukebox in v3.19 or any other prior version of MorphOS that I have tried them with over the years prior to v3.19. It is only v3.20's release that is causing this issue, and as I have said that includes running it from the MorphOSboot CD, so MOSSYS / Jukebox in v3.20 is doing something that it doesn't do with any other release!

If I replace only the MOSSYS of v3.20 with the MOSSYS of v3.19 all works without issue, and I can even use the release of Jukebox that comes with v3.20 with the v3.19 MOSSYS without any problem, but it "freezes" with v3.20, it is as simple as that, and I have spoken with cyfm on the topic briefly though I know he is not currently available for more detailed assistance right now, but he has offered his assistance when he becomes available again, as he too, like jacadcaps, owns an iMac A1145 which is the system that is manifesting this "bug" with my hardware.

Though thanks for your interest, and suggestions as to how to resolve the issue.

Quote:

Did you do the dichotomic search for the offending MP3 breaking the system?
Where is the playlist?

If you don't give us what's needed to reproduce your case, we won't be able to fix anything. Case closed for me as you're likely not willing to provide the requested information.

@ Tcheko - that is entirely not the case, and I more than willing to agree to assist, ideally just jacadcaps at this stage. My delay in replying is due to having been engaged elsewhere, with other issues - as life, and all that goes with it, does need attending to from time to time as well!

I said I was going to pass my findings back to jacadcaps, but the Playlist as such is a whole directory of MP3s, WAVs, AACs, etc. and it is 11.3GB in size (not the playlist but the directory, so passing you all the files details would take up a large amount of space on here, and so sending whatever details jacadcaps needs by email seems a better solution for me. If he then decides to pass any of that information on to you then by all means he has my agreement to do so, at this stage, but I am going through the directories basically as advised to identify at which point the system freezes. Hold on, with a bit of patience, and I feel sure I will get to the point where you as a developer needs to be to asses the impact of this "bug" to fix it.

Thanks for your interest in this issue.

[UPDATE] - I have forwarded my checks loosely based on the "dichotomic search" and some of the audio files in my music library to jacadcaps, with what seems to be conclusive as to the cause of the "freeze". I believe I "short-circuited" this search by just loading a wide variety of varying filetypes and this brought about an almost immediate "freeze". So, as you have shown interest (Tcheko) I will send you a PM with some of that information, so you can get as involved as you want to, and maybe get in direct contact with jacadcaps for any additional details you feel you need to know, and once again thanks for obvious interest in resolving this issue that has affected my iMac with this outage.

Quote:

Amazing. Instead of saying straight that you're in fact loading a directory full of various audio file formats, you tell us that you're loading a playlist of MP3...

I feel exhausted.

@ Tcheko - if only my way of wording loading those music files tires you out, then go and have a lie down, though doing that bit of sideways thinking doesn't really justify being exhausted, does it?!

Go and have an energy drink or a banana or something to top up your energy levels:-?

Quote:

It is about you presenting your evidence. Pages long mail and posts alternating giving little information each time.

I first had the impression for several days that any file is causing the JukeBox crash, then you gave Jaca the information about loading a playlist with 12K files and now it is not even a playlist, but a folder with music files you opened.

You should really work on the form you present stuff. If your goal is to piss off every MorphOS developer you are on a good way.

I alone got several mails with several bloated pages of text, where you failed to provide any useful information beside some breadcrumbs hidden in gigantic text blocks, where you are waffling around on the same facts over and over that you found out and where we where wrong.

And stop using all the text style changes. It is annoying.

However, credits to jPV, he found out that .ogg files are the problem and delivered two files causing trouble, so the bug could be isolated and fixed. This is how it works.



[ Edited by geit 10.06.2026 - 22:30 ]

I seem to remember you saying, Quote:How many users over the years installed the Chrysalis Pack of software to enhance their base setup? So, how many other MorphOS users should your comments to me also apply to? You would probably only have 25%, or less, of the registered users left if you went that route!

In any case, I had no idea that some of the files were going to get placed incorrectly, or where they actually got placed, and I suspect many other users, as novices, as I was back in 2012, would have been, and may still be, in the same position. There was no information available that some files were known to have been installed incorrectly, and which files they were, so that they could and should be removed. My system, when you identified this as a potential problem to the stability of my system was taken very seriously by me, and I removed those files from my system very quickly.

As it turned out those errant Chrysalis Pack files had not caused this problem, they were basically "dormant", but I am grateful that you identified them to me, as it has allowed me to remove them so my system is more likely to be inline with a standard MorphOS system, with the system directories only containing the files they should.

I still consider that it was somewhat extreme of you to say to me those comments that you made, while not even considering that my comments were factually correct . . . as it is something in v3.20 that was the cause of this "freeze". As you completely ignored my factually correct assessment, and became "blinkered" in focusing on the issue as being the Chrysalis Pack's residual files that were the cause of the "freeze" . . . that was incorrect, and from my standpoint poorly considered as you never looked into my report at all AFAIK.

You ended up blaming me, and basically shunning me (your comments above speak directly of that), for identifying an issue that v3.20 has become wrongly endowed with, while failing to check out the report, or ask me for more details that would have correctly identified this issue, much sooner. Do you think that all other users that installed the Chrysalis Pack should also be "shunned"?

I agree with you, Quote: However, there should be some guidance as to how to fix them ideally, if the user has made that "mess" inadvertently and installed some software "in good faith" that it would not cause such a problem. After all the overall stability of users' systems is also in the best interests of the MorphOS Development Team, so there are fewer or no false reports of issues. I did not need much help to realise what had been left on my system, after your guidance, and my system has been "exorcised" of those files now.

I have said it before, for me, the Chrysalis Pack was a quick way to enhance the MorphOS system, but I did not realise that some files, and software might be potentially errant or harmful, as the Pack had been around for quite a few years, with no mention that I came across, back in 2012, that stated it was, "install it at your own risk, and you are now excommunicated from support from MorphOS!"

Surely there is no need for such vehement comments now. I have identified the problem as not being mine, but something in v3.20, that ideally should not have slipped through the betatesting, though we are all human, and anyone, even a very experienced beta testing team can inadvertently allow the occasional error, or mistake in their oversight to occur, if I have identified the situation correctly.

Quote:
For my part, I never demanded, yelled, cried that the MorphOS Team had changed something. I tried to explain what I had encountered, but found you focused on the Chrysalis Pack's potential for creating trouble for the MorphOS system, by overriding features and files that were intended to keep the system stable. I accept that the Chrysalis Pack had issues, but they were known to you in the MOS Dev. Team, not really to me as a novice user in 2012, and no-one from the team spoke to me about the potetntial issues it might cause back in 2012, or at any time since then up until this current date, and I did not see any forum threads, certainly not active ones, that identified such issues.

With regard to my own non-MorphOS system, it is me that maintains them, like I removed the errant Chrysalis Pack files. It is always beneficial to have guidance from an expert such as you, which I appreciate, though you, sadly, probably don't believe me.

I did say in a previous thread that . . . Quote: Your reply, and I cringe (wished that you had not said them) at the words you used Quote:
You offered no support, for what has turned out to be a valid issue it seems, and all you offered was no future support, as a result of installing the Chrysalis Pack that I installed "in good faith" back in 2012 - 14years ago, with no adverse system errors that directed me back to ask for support during that time, apart from to ask recently about LoView and now v3.20's "freeze"!

Quote:
It is all very well saying that in 2026, but in 2012 the Chrysalis Pack was basically all there was, apart from Grunch that offered some update(s). Whereas the Chrysalis Pack offered enhancements that included additional skins, pointers, wallpaper, icon packs, default icons, utilities, tools, programs (applications), etc., all of which together were too tempting to ignore when initially starting out with MorphOS for me.

Why doesn't the MorphOS Development Team, knowing that there is probably a demand for such additional customisations, make an "authorised" pack available for new and established users to enhance their systems, knowing that the files that are going to be added to a system are then not going to adversely affect the stability of its system, yet allow users to modify, and customise their systems correctly, in keeping with MorphOS's system structure?

Many users took up using MorphOS as an alternative to OS4 that had failed to deliver IMHO, whereas MorphOS had faster hardware, was easier to acquire, and cheaper to afford, with many pieces of Apple G4 and G5 hardware available to choose from, easily the BEST Amiga-like Next Generation system available, and still is IMHO.

Quote:
I seem to remember that I was trying to convince you that it was an issue in v3.20 . . . not the Chrysalis Packs remnant files that were still on my system, but you did not seem to want to know that it was a MorphOS issue!
Quote:
You did not reply in this thread for over 2 days, and I never got a reply back from you about any of the details I passed you, so how would I know what the "impression" was that you had formed. You have to communicate, and ask questions if I have not explained something sufficiently to you, to find out what I had observed, rather than "shun" me by telling me I am "now on your own", for an incorrect judgement you accused me of about installing the Chrysalis Pack in 2012!
Quote:
I tried to get you to see that it was not the Chrysalis Pack that was the issue, but that it was MorphOS v3.20's release that had the issue that was causing my system to "freeze", but as then, as your above comments bear out, and even now you are not really acknowledging that v3.20 is where the issue resides. You only needed to reply to me with specific questions as to what I had observed in as much detail as I could offer, and I would have elaborated where necessary.

What is the difference between a PlayList, and a List that you Play? I added the files to Jukebox to play, and it made a list! There is little difference between the two methods of getting some music files to play, it is a moot point IMHO. However, if you had decided that it was a MorphOS v3.20 issue, instead of focusing on it being a Chrysalis Pack issue, then you could have, and should have, focused on that, and checked out my observations, that I reported to you in "good faith" in a timely manner, and asked me any questions that would have assisted you in detemining where the problem lay, but I feel certain your focus was on it not being a MorphOS v3.20 problem and merely the Chrysalis Pack's, and my own as a "dumb" user's, fault!
Quote:. . . That you never got back to me about their content, to ask any relevant questions to isolate the information you needed to know. No communication, no further explanation!

I would have hoped that this "bickering" would not have occurred, or that you would not have intimated that I was now to be "shunned" for adding the Chrysalis Pack onto my system, over 14 years ago, in "good faith". That seems to me to be where you focused your thoughts and comments, as the Chrysalis Pack only being the issue that had caused this "freeze".

For my own part I had no intention for this back and forth of unnecessary comments to happen, or by anyone else in this thread. I had only the intention to pass back that I had come across a problem with v3.20 and it caused my system to "freeze" and for it to be taken on-board seriously, but it was not, and no amount of complaining about long emails that you never replied to can fix a problem that you failed to grasp as a MorphOS issue . . . which it is!
Quote:
Yes it is!

There is a bug in MorphOS Reggae Ogg Vorbis demuxer (ogg.demuxer). Unfortunately the nature of the bug is that any Ogg Vorbis file with negative stream serial number being processed by Reggae will cause a hard crash. ogginfo tool (part of vorbis-tools) can be used to identify the files that cause the crash. For example on a linux system, to check all .ogg files in current directory that will cause issues:
Code:

If you absolutely cannot risk a crash we recommend deleting ogg.demuxer from 3.20 install with:

Code:

This will effectively disable the broken Ogg Vorbis support and prevent a system crash.

A proper fix to this issue will be released as part of MorphOS 3.21. Special thanks to jPV for the delivering sample files demonstrating the problem.

[ Edited by Piru 11.06.2026 - 01:24 ]