forty-two kernel panic

[cremegg]

Hi

I am/was attempting to create an SVCD of SW Ep 2 (PAL, Region 2). The 1 minute test clip encoded nicely and then forty-two set about xffering the video, completed that succesfully. Video transcoded succesfully. Then it started audio processing, I watched as the file size grew then at around 200MB plus it stopped and I waited for it to move on but it didn't. I went to bed and when I woke up in the morning my mac had paniced. I decided to try just a short chapter encode and again my macintosh paniced. Fearing it may be the DVD I decided to try Ice Age (PAL, Region 2) but I hit the same problem. This problem also arose when attempting to create a VCD.

Thinking it may be a problem with updating I erased all forty-two files and installed 1.5 from the installer but I have experienced the same problems.

I have not used the 'speedup.'

Any suggestions or thoughts?

Also I read the documentation so forgive me if I missed the answer to this question. Does DivX output support subtitles? I attempted to create a nDVD DivX of SW Ep 2 to find the subtitles I was after but after the PreCaching the DVD was ejected and forty-two said it had completed. So I tested the chapter encode without subtitles and it was fine. Could this be because all the subtitles are labelled 'en'?

[KaiCherry]

Hi

I am/was attempting to create an SVCD of SW Ep 2 (PAL, Region 2). The 1 minute test clip encoded nicely and then forty-two set about xffering the video, completed that succesfully. Video transcoded succesfully. Then it started audio processing, I watched as the file size grew then at around 200MB plus it stopped and I waited for it to move on but it didn't. I went to bed and when I woke up in the morning my mac had paniced. I decided to try just a short chapter encode and again my macintosh paniced. Fearing it may be the DVD I decided to try Ice Age (PAL, Region 2) but I hit the same problem. This problem also arose when attempting to create a VCD.

Its probably your RAM.

Also I read the documentation so forgive me if I missed the answer to this question. Does DivX output support subtitles? I attempted to create a nDVD DivX of SW Ep 2 to find the subtitles I was after but after the PreCaching the DVD was ejected and forty-two said it had completed. So I tested the chapter encode without subtitles and it was fine. Could this be because all the subtitles are labelled 'en'?

This is in fact a bug. Just discovered and confirmed today in fact. It will be fixed in by the 25th (see? not so bad to have it expire now, is it?) assuming we don't shoot ourselves in the head first

Thanks for the *legit* bug report and the detailed info. And check out that RAM.

-K

[cremegg]

And check out that RAM.

One thing I forgot to mention in my post, I did get succesfull SVCD ouput from forty-two 1.02 without panics.

Do you think it could be a physical problem with the RAM? I can almost positively say I've never had a Kernel panic before. I have 1.5GB RAM and use fairly memory intensive applications regualarly obviously without incident.

Still think it could be the RAM?

[KaiCherry]

Still think it could be the RAM?

When I worked in service, for single cpu machines this was the problem over 90% of the time.

For the duals, it was gernerally failing cache ram of the cpu daughtercard.

Since none of us developing forty-two have ever had a KP running for days and days on end since its embryonic versions in December, and the fact that it doesn't do anything outside of UserSpace but work the RAM, HD and CPU I'd look at the hardware.

10.2.x is really *not* supposed to do this It ain't 9

-K

[cremegg]

A tech minded friend helped me locate the cause of my KP (/Library/Logs/panic.log, why don't they tell people about these handy logs!). The panic.log indicated that the panic was due to 'com.apple.iokit.CHUDProf' so I removed CHUD from my system and restarted.

There still however seems to be an issue for me when creating an SVCD. I did a small chapter test using a VBR of 5 (Q3 indicated in the progress window) and forty-two is still stalling after the audio processing.

I encoded the chapter with another application so I know the audio should be 6.6MB. But when forty-two reaches 6.6MB the file stops growing but it still indicates that it is processing the audio. To be sure it wasn't doing anything else and that there was no longer a KP issue I left forty-two running over night again but when I went back it still seemed to think it was processing audio but hadn't paniced about it this time.

[cremegg]

A new user to this forum PM me to say he is having the same problem.

Hi, I'm new to this vcdhelp forum and i'm not yet able to post in forum. Anyway, i have the same problem as you have described.

[KaiCherry]

A tech minded friend helped me locate the cause of my KP (/Library/Logs/panic.log, why don't they tell people about these handy logs!). The panic.log indicated that the panic was due to 'com.apple.iokit.CHUDProf' so I removed CHUD from my system and restarted.

There still however seems to be an issue for me when creating an SVCD. I did a small chapter test using a VBR of 5 (Q3 indicated in the progress window) and forty-two is still stalling after the audio processing.

I encoded the chapter with another application so I know the audio should be 6.6MB. But when forty-two reaches 6.6MB the file stops growing but it still indicates that it is processing the audio. To be sure it wasn't doing anything else and that there was no longer a KP issue I left forty-two running over night again but when I went back it still seemed to think it was processing audio but hadn't paniced about it this time.

Standard reply:

"forty-two does not claim to work with every DVD out there."

That said, what dvd is this? Have you tried a different one?

Thanks,

-K

[cremegg]

Standard reply:

"forty-two does not claim to work with every DVD out there."

That said, what dvd is this? Have you tried a different one?

Thanks,

-K

I can understand that KaiCherry all I am trying to do is provide feedback to forty-two users and developers, but it seems odd to me that the .mpa and .mpv are created without any problems but are failing to MUX.

I have had the same problem with Star Wars Episode 2, other people have reported success with this DVD and Ice Age. Both PAL, Region 2. I am currently testing Star Wars Episode 1, PAL, Region 2. These are the only DVD's I have tested with forty-two 1.5 to date.

[Flip Flop Frog]

Hey Kai,


I've been having the same problem too... The first versions of 42 worked perfectly fine for me, and the newest versions are causing kernal panics part way through.


I did an extnesive hardware test on my RAM chips, 512MB of DDR 333MHz and I've found that there is apparently nothing wrong with it.




Any more ideas?

[rockinsage]

I've been having the same problem too... The first versions of 42 worked perfectly fine for me, and the newest versions are causing kernal panics part way through.

This is happening to me as well. I don't seem to be able to get throgh an SVCD encode without KP'ing with v1.5. The panic.log unfortunately didn't help me, because it didn't capture any data on this KP. Oh well... back to 1.02...

[El Claudio]

A Kernel Panic happened to me also when trying to make VCD. Maybe if you do a search in the forum you'll find my post. All the developper could answer : RAM related problem. Man... I'm so happy to see that so many Apple computers have the same problems as I do with the forty-two app. Damn Appple, they don't know how to make good forty-two computers ready!

All right, being sarcastic here. I find it funny to see a developper blaming hardware, Bill Gates was already using that line years ago about his Window$...

[KaiCherry]

Hey, ass...check this out...

forty-two does NOT DIRECTLY ACCESS RAM, DEVICES or HARDWARE. MacOS X is a PROTECTED MEMORY OS, so if you are having Kernel Panics it is most likely YOUR SYSTEM.

I know all Mac Users are perfect, fault-free individuals.

Here's an idea...RUN A HARDWARE TEST.

If everything passes, CHECK THE PANIC LOGS. I'll betcha that "forty-two" or ANY of its associated apps won't be there...you know why?

This ain't OS9, slick.

Now that *my* "sarcasm" is out of the way...

Check the panic log. 99.99999% chance you are having either 1. memory access violation problems (RAM failures) 2. Hardware/driver issues (something patching into iokit is stomping kernel space) or 3. *Apple's* (oh no, not Apple!!) own stupid CHUD profiler is going screwy and crashing your machine.

Go on...check it out. Email chris via our website...in *every* case of these so-called "forty-two" related KP's is been one of those three things...

Because again folks, *forty-two runs in user space and has NO DIRECT ACCESS TO THE HARDWARE*

You post here asking for help, or clues, or whatever. You don't like the answer? Sorry.

If you'd like me to take credit for the impossible, fine. forty-two, thru means it is completely incapable of, is causing MacOS X to panic, even tho' it has no way to do so.

My suggestion is that you erase forty-two and use something else, because this...bug...will never, ever, ever be fixed by me.

Because I'm not causing it.

-K

A Kernel Panic happened to me also when trying to make VCD. Maybe if you do a search in the forum you'll find my post. All the developper could answer : RAM related problem. Man... I'm so happy to see that so many Apple computers have the same problems as I do with the forty-two app. Damn Appple, they don't know how to make good forty-two computers ready!

All right, being sarcastic here. I find it funny to see a developper blaming hardware, Bill Gates was already using that line years ago about his Window$...