"Segmentation fault" in thread "MainThread", at address 0x0

[digidub]

Hey all, I've been getting a strange error tonight. It occurs anytime I try to move a Quicktime Movie onto a second display. The error is:

"Segmentation fault" in thread "MainThread", at address 0x0

I hit ok and then Pro Tools just crashes.

I've gotten this error in the past, as well as the "Bus Error," during heavy sessions, but tonight is the first time the errors are easily repeatable. Strange because yesterday this was not happening. i even made a new session with nothing but the video in the session, and moving the ref to the seond display causes the error. Any suggestions? DigiTechSupport?

PT 8.0.1cs3
10.5.8
Mac Pro 2x3.0gHz
6GB RAM

[Ryan.Drum]

Hi,

Also having the same error, however it occurs when I attempt to import WAV files that I recorded on another session.

Please help!


iMac i5 2.8GHz
4MB RAM
Mac OS Snow Leopard
Pro Tools 7.0.4 LE

[Vedat]

Digidub, I recommend upgrading to 8.0.4.

Ryan, I am amazed you can even run PT LE 7.0.4 on Snow Leopard.

This error is apparently related to how PT manages the computer memory, so potentially could be Memory related.

[DigiTechSupt]

Originally Posted by digidub

Hey all, I've been getting a strange error tonight. It occurs anytime I try to move a Quicktime Movie onto a second display. The error is:

"Segmentation fault" in thread "MainThread", at address 0x0

I hit ok and then Pro Tools just crashes.

I've gotten this error in the past, as well as the "Bus Error," during heavy sessions, but tonight is the first time the errors are easily repeatable. Strange because yesterday this was not happening. i even made a new session with nothing but the video in the session, and moving the ref to the seond display causes the error. Any suggestions? DigiTechSupport?

PT 8.0.1cs3
10.5.8
Mac Pro 2x3.0gHz
6GB RAM

How is that second monitor connected? Does this happen with every video or just this particular one? What format is the video (size, compression type, etc.)?

Have you tried 8.0.4 yet?

[digidub]

I havne't upgraded yet, but I plan to this week since I just finished a project.

I still get this error randomly with any session (seems to happen more regularly the more intensive the session - tons of edits, automation, etc), but for that particular session back when I posted, I think I got around it by reoutputting the video track(s) in FCP before importing, but I'll have to dbl chk and get back to you.

I have only experienced video-related error with those videos, other videos I've had no issues.

It's a second DVI output on my vid card.

[DigiTechSupt]

Originally Posted by digidub

I havne't upgraded yet, but I plan to this week since I just finished a project.

I still get this error randomly with any session (seems to happen more regularly the more intensive the session - tons of edits, automation, etc), but for that particular session back when I posted, I think I got around it by reoutputting the video track(s) in FCP before importing, but I'll have to dbl chk and get back to you.

I have only experienced video-related error with those videos, other videos I've had no issues.

It's a second DVI output on my vid card.

If reexporting the video helps, and you seem to only have problems with those specific videos, I would think there's some kind of corruption in the video itself. If the reexport is using the exact same settings as the original, then corruption would almost assuredly be the case. If you're using different settings, it may be a bug or other issue with the app creating the file or possibly with the codec being used.