I have a strange problem that I really don't know how to solve:

when compiling patch using jitter as standalones, they run on some PC

and don't on some other, that are not so different...

The patch is quite complex and I was finally able to find out the crash

on startup was due to jitter after removing parts of the patch one after

another, and noticed it was crashing as soon as there was any jitter objet

in the patch (I didn't try with all of them, but it crash with GL and non

"The instruction at "0x02519b87" uses the memory adress "0x7ffddFFF"

The memory could not be read. Click OK to finish the program"

with an OK button and not error detail... or there is no message at all.

The same patch doesn't seem to crash as collective, though it implies

modification in the patch that I didn't finalize.

The standalone crash as soon as the message "jitter 1.6.3b2 installed"

shows up in the max window when the standalone app starts.

The crash appears with the following system specifications:

- Windows XP professional version 2002 service pack 2

- PC DELL Inspiron 9400 Intel Core 2 CPU T5500 @ 1.66Ghz

while it doesn't crash on other PCs with these specifications:

- PC DELL Inspiron M1710 Intel Core 2 CPU T7200 @ 2.00Ghz

Support folder from standalone contains jitlib.dll

I have been compiling this application many times without much problem,

eventually including all ressources from Cycling74 folder in the support

Does anyone have any idea how to get the standalone run without crash?

Maybe there is a crashlog somewhere, but I wasn't able to find it for

standalone app crash (and since the crash doesn't appear in Max, there

I have a strange problem that I really don't know how to solve:
when compiling patch using jitter as standalones, they run on some PC
and don't on some other, that are not so different...
The patch is quite complex and I was finally able to find out the crash
on startup was due to jitter after removing parts of the patch one after
another, and noticed it was crashing as soon as there was any jitter objet
in the patch (I didn't try with all of them, but it crash with GL and non
GL objects).

There is either a message saying :
"The instruction at "0x02519b87" uses the memory adress "0x7ffddFFF"
The memory could not be read. Click OK to finish the program"
...
with an OK button and not error detail... or there is no message at all.

The same patch doesn't seem to crash as collective, though it implies
modification in the patch that I didn't finalize.
The standalone crash as soon as the message "jitter 1.6.3b2 installed"
shows up in the max window when the standalone app starts.

The crash appears with the following system specifications:
- max 4.6.3 , jitter 1.6.3b2
- Windows XP professional version 2002 service pack 2
- PC DELL Inspiron 9400 Intel Core 2 CPU T5500 @ 1.66Ghz
- 2Go RAM
- ATI mobility Radeon X1400

while it doesn't crash on other PCs with these specifications:
- max 4.6.3 , jitter 1.6.3b2
- Windows XP professional version 2002 service pack 2
- PC DELL Inspiron M1710 Intel Core 2 CPU T7200 @ 2.00Ghz
- 2Go RAM
- NVIDIA GeForce Go 7900 GTX

Support folder from standalone contains jitlib.dll
I have been compiling this application many times without much problem,
eventually including all ressources from Cycling74 folder in the support
folder of the standalone application.

Maybe there is a crashlog somewhere, but I wasn't able to find it for
standalone app crash (and since the crash doesn't appear in Max, there
is no such crash info in max crash log)

jitter-standalone-crash-on-pc

what if you make a standalone with just "jit.qt.movie" in the patch (the simplest jit patch possible?)? Does it crash?

Sorry to start with the obvious, but...Is Quicktime fully installed on the crashing machines?

what if you make a standalone with just "jit.qt.movie" in the patch (the simplest jit patch possible?)?  Does it crash?
Sorry to start with the obvious, but...Is Quicktime fully installed on the crashing machines?


jitter standalone crash on PC