vichug

it's all in the title, i'm trying to open reference of objects in max 7.0.1 and it crashes max instantly

several times but not always, i have the "max is constructing database" with % display at the launch. Sometimes it goes to the end, sometimes not (it crashes in the middle). Sometimes it goe sto the end then doesn't crash, will crash later.

I have max 6.110 installed as well. I'm on Yosemite. Reference in 6 is opening without the slightest flaw. I'd rather stay away from 7.0.3 for now, because there are several bugs noticed by users since 7.0.2 that don't seem to have been adressed (see the 7.0.2 update thread). But i'm not sure, maybe i did something wrong in my install, not sure updating would help. maybe reinstalling would ? also i tried to change the name of the Max application to Max7 without improvement, so i changed it back.

I'm concerned it might be a clash with max 6. Or maybe something wrong in my installation ? Is it possible that a bad package causes such problem ? (ie, i have the BEAP package from Git installed alongside the max native one, so my beap modules are detected twice)

I tried trashing the preferences (both the .maxpref and the .json) to no avail.

hello
it's all in the title, i'm trying to open reference of objects in max 7.0.1 and it crashes max instantly
several times but not always, i have the "max is constructing database" with % display at the launch. Sometimes it goes to the end, sometimes not (it crashes in the middle). Sometimes it goe sto the end then doesn't crash, will crash later.
I have max 6.110 installed as well. I'm on Yosemite. Reference in 6 is opening without the slightest flaw. I'd rather stay away from 7.0.3 for now, because there are several bugs noticed by users since 7.0.2 that don't seem to have been adressed (see the 7.0.2 update thread). But i'm not sure, maybe i did something wrong in my install, not sure updating would help. maybe reinstalling would ? also i tried to change the name of the Max application to Max7 without improvement, so i changed it back.
I'm concerned it might be a clash with max 6. Or maybe something wrong in my installation ? Is it possible that a bad package causes such problem ? (ie, i have the BEAP package from Git installed alongside the max native one, so my beap modules are detected twice)
I tried trashing the preferences (both the .maxpref and the .json) to no avail.


max-7-0-1-constant-crashes-when-opening-reference

reinstalling did help !... i could open 7 and open a reference once or twice

BUT HERE IS THE cATCH if i close, then open 6, then try to reopen 7, it won't open at all, crashing during the opening operation.

i would very very much like to know what can be the cause of this. But definitely, a conflict between max 6 and 7 is a beginning of the answer.

I'm going to reboot my computer now. Who knows...

reinstalling did help !... i could open 7 and open a reference once or twice
BUT HERE IS THE cATCH if i close, then open 6, then try to reopen 7, it won't open at all, crashing during the opening operation.
Now 7 doesn't open at all.
i would very very much like to know what can be the cause of this. But definitely, a conflict between max 6 and 7 is a beginning of the answer.
I'm going to reboot my computer now. Who knows...


after rebooting, max 7 rebuilds database on launch, and doesn't crash when opening a reference (probably the problem is with the whole documentation/database system anyway). It works at least twice.

Then for the max 6 test : opening max 6, opening a ref page

So do i have to reboot my computer each time i want to use max 7 after having opened max 6 now ?

after rebooting, max 7 rebuilds database on launch, and doesn't crash when opening a reference (probably the problem is with the whole documentation/database system anyway). It works at least twice.
Then for the max 6 test : opening max 6, opening a ref page
closing max 6, opening 7
aaaand it's gone. Same as previously.
So do i have to reboot my computer each time i want to use max 7 after having opened max 6 now ?


I also noticed some instability with the reference in Max 7.0.0, 7.0.1.

I recommend archiving your current max.app and trying 7.0.3.

(RE issues with Max 7.0.2, 7.0.2 II have not experienced any jit.phys irregularities in 7.0.2 or 7.0.3).

I cannot reproduce the reference issues you're experiencing in 7.0.2 or 7.0.3, including opening Max 6, Max 6 reference pages, and then opening Max 7 Reference. My test used OS X 10.10.3. However I am on Ma 6.1.9.

Max 7 will rebuild database when a new version is installed and on app launch. In 7.0.3 I believe there is a fallback reference resource if the database is building.

If the database is weird try sending ; max db.reset to Max 7, allowing the database to rebuild (progress shows in the Max Browser), then quit and restart Max 7.

I also noticed some instability with the reference in Max 7.0.0, 7.0.1.
I recommend archiving your current max.app and trying 7.0.3.
(RE issues with Max 7.0.2, 7.0.2 II have not experienced any jit.phys irregularities in 7.0.2 or 7.0.3).
I cannot reproduce the reference issues you're experiencing in 7.0.2 or 7.0.3, including opening Max 6, Max 6 reference pages, and then opening Max 7 Reference. My test used OS X 10.10.3. However I am on Ma 6.1.9.
Max 7 will rebuild database when a new version is installed and on app launch. In 7.0.3 I believe there is a fallback reference resource if the database is building.
If the database is weird try sending ; max db.reset to Max 7, allowing the database to rebuild (progress shows in the Max Browser), then quit and restart Max 7.


oh, okay. Thanks for the tips. I tried a 

 (wasn't reminding the correct command name). But maybe the problem comes from the fact that the 6.1.10 build date is more recent thant the 7.0.1 build date ? idk.

oh, okay. Thanks for the tips. I tried a ;max reset ; did not try a ;max db.reset (wasn't reminding the correct command name). But maybe the problem comes from the fact that the 6.1.10 build date is more recent thant the 7.0.1 build date ? idk.


max 7.0.1 constant crashes when opening reference