QT Player 7.0.2 crashes when encoding from MJPEG into H.264

Question

Another interesting thing about QT 7.0.2 (first one was 10GB bug, check my earlier thread here) - it crashes when the user switches to another account and back while the QT Player encodes MJPEG video into H.264. How to reproduce this bug, step by step:
1) open any MJPEG video in QT Player 7.0.2, could be in MOV or in AVI, doesn't make difference which
2) do File->Export
3) choose "Movie to QuickTime Movie" in the "Export" drop-down menu
4) in the "Save exported file as" dialog go to Options->Video->Settings and set H.264 as your output video codec, encoding settings don't make a difference as well
5) close "Movie settings" dialog, then click "Save" in "Save exported file as" dialog
6) QT Player starts encoding your MJPEG video into H.264 video, the small "Progress" window appears with a progress bar inside
7) now switch to another user account using Fast User Switching feature of Windows XP
8) switch back to the account where QT Player was encoding your MJPEG video
9) observe the crash window - your QT Player has joined his ancestors now
Can anyone reproduce this? If yes, please post your crash dump here, so that I can send another bugreport to Apple (10GB bugreport is in the works now, almost done
If you follow all the steps above and your QT Player does NOT crash, please post the details about your system. My setup is QT Player Pro 7.0.2 and Windows XP Pro SP2. Also post the details about your MJPEG file - the codec you used to encode it (mine two codecs were Pegasus PicVideo 3 and Apple Motion JPEG A), and the resolution (mine was 720x480).

Answer 1

when i said i couldn't do audio and video at the same time i meant that i cannot edit and process video and at the same time record or edit ADR, sound effects. i have an audio engineer in the audio room working on the audio while i work on the video. is that clear?
Yeah, now it sounds reasonable. You possibly could do that on a single computer using X Windows or Windows Terminal Server but it's totally different topic.
as for fast user switching...here's a comment from another forum... "just don't use fast user switching, it isn't implemented well and it breaks some programs"
"Don't use Windows, it isn't implemented well and doesn't run some poorly written MS-DOS games"
I found several others in that regard, but you know more about it so i don't need to post links, right? plus a lot of them dealt with quicktime, but again you are the expert.
If you found anything that's related to QuickTime crashes during account switching, you're welcome to post this concrete info here, it'll help with my bugreport.
and since you make the inference that i have a cheap system operating on ms-dos which is laughable because that means that you can't read.
I said that when I read about single-task computers this reminds me about MS-DOS times, but now it looks like it is not about your case, since you have two people working in parallel on two machines.
i looked up on Yahoo! the terms "mjpeg"+"crashes" and got 16,800 hits. plus i do recall on another forum someone was having problems with mjpeg and the responder said it wasn't a good codec to work with...
So what's the deal if 95% of these 16800 Yahoo posts are about crash in Premiere or Microsoft Movie Maker or some other buggy tool? You could even search for an f-word, and you'll find a lot of posts with that word, then you can make any conclusion you like about that word being so often cited and then we could start a lengthy discussion about it, but what's the point? I can find 10000 posts about "single task" + "bad" but I'd never use this to justify anything. I give you concrete facts from my experience, so please give me something concrete in return, not 16800 Yahoo posts about something out there.
"Disadvantages: There's also the problem of recompression. While the human eye can be fooled by JPEG's compression, computers aren't. Thus, when you compress from MJPEG into another format to use for distribution, you will receive a lower-quality picture than if you had a lossless source because there is data missing which, while it's not important to the visual cortex, is very important to a mathematical analysis of things such as color data. The only time you should use MJPEG otherwise is for fast-editing temporary files, but DON'T use them as your final source."
I know that already, thank you.
since you said i'm the one who suggested that you use uncompressed video and that doing so the computer doesn't crash...
You suggested that in a different thread about 10GB MJPEG limitation. That's another bug that may be or may be not related to the crash problem.
then why don't you work that way and finish your video?
Yes, I can employ this trick. I will do it if I'm forced to (i.e. if I absolutely have no other way to load MJPEG in QT Player and Apple refuses to fix that crash). However, I'll push Apple with fixing the issue at the same time. Maybe they'll work something out while I'm using uncompressed RGB workaround or some other workaround.
mjpeg is unstable in that regard so contact the codec manufacturer/developer and ask them why or give them the bug report because it's not apple
Unfortunately it is Apple, because it's the Apple's software that crashes. All the other codecs and video editors work fine, and there are even conditions when Apple doesn't crash, like loading uncompressed RGB. Since crash is inside QuickTime I will send my bugreport to Apple. If the crash had happened inside the MJPEG codec, I'd have sent the bugreport to