Author |
Topic |
|
alsystems
Junior Member
USA
116 Posts |
Posted - 18 Jul 2014 : 08:17:34
|
I believe the operating limit on 32-bit version of XMM is:
Database Size > ???MB (probably between 775MB and 1100MB)
Question for maulens: What are your database specs?
Edit: I noticed that 1103MB of RAM is used by XMM according to the task manager. It seems when this allocated amount is exceeded (large database), the database crashes. |
Edited by - alsystems on 14 Oct 2014 04:45:49 |
|
|
newsky
Starting Member
Russia
1 Posts |
Posted - 22 Jul 2014 : 11:38:15
|
Hello. Same problem. Works only till I click a film in the list or immediately crashes.
1.500 films, 63.000 actors, 1.2Gb base. |
|
|
VSUK
Starting Member
13 Posts |
Posted - 13 Oct 2014 : 08:59:17
|
I'm having this same problem. Have you managed to find any solutions?
Many Thanks,
VS |
|
|
VSUK
Starting Member
13 Posts |
Posted - 14 Oct 2014 : 14:24:31
|
Further to the above, and after monitoring XMM closely using task manager, XMM is crashing at around 700MB of memory usage, not exceeding or getting anywhere near the allocated amount of 1103MB.
Script updates of up to 10-15 movies work (imdb complete) work ok if only run once. The second runs (if you update another batch of movies) are the ones crashing. You have to restart XMM to be able to update / run another batch of movies. Second runs crash with just one or two movies. |
Edited by - VSUK on 14 Oct 2014 17:06:23 |
|
|
alsystems
Junior Member
USA
116 Posts |
Posted - 15 Oct 2014 : 02:50:58
|
VSUK,
I would conclude you've reached some physical limit of the x32 version of XMM. I have not been able to determine precisely what this limit is.
Like you've guessed, probably only the x64 version would handle your large XMM database. The x64 version was released and then removed due to bugs. I don't know what it's current status is. Here is Ale's direct email address: Alessio Viti <alessioviti@binaryworks.it> |
|
|
VSUK
Starting Member
13 Posts |
Posted - 16 Oct 2014 : 08:58:35
|
Thanks, Alsystems
I have emailed Ale about the x64 version, but have not had a response yet.
Very frustrating, mainly because of the time I've already spent on this - I'm too far into it, but had I known what I know now I would not have used XMM.
|
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 02 Nov 2014 : 10:08:37
|
Second that |
|
|
Alessio Viti
Forum Admin
Italy
9171 Posts |
Posted - 03 Nov 2014 : 15:36:33
|
Hello Guys,
I have upload just now a new release.
I have made some tests to try to figure out the 64 bit drivers problem.
Now the EXE should run correctly in both systems.
If you have a 32 bit windows, nothing will change.
If you have a 64 bit version probably you need to install the database drivers.
If XMM will not be able will automatically open the website to download the Drivers.
Alessio |
http://www.facebook.com/pages/eXtreme-Movie-Manager/47220214342?ref=mf
|
|
|
VSUK
Starting Member
13 Posts |
Posted - 03 Nov 2014 : 18:38:00
|
Thank you, at glance (still testing) it seems to have stopped crashing. VS
|
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 19 Feb 2015 : 15:37:01
|
Hello
It still deletes the mdb file if i compact database from xmm8 64 bit. |
|
|
wellwet
Junior Member
Turkey
103 Posts |
Posted - 26 Feb 2015 : 12:35:46
|
@DrunkBell reported this months ago, still a bug :( And returned to 32 bit because of slowness.. |
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 27 Feb 2015 : 23:02:42
|
Ok here it goes, i re-updated all movies with 12 actors limit, there are 5510 movies and 70K actors/directors etc... DB size is 1,15 GB, i choose update everything for actors since i want to see photos, it also brings gender, occupation and death date(no birth date) which are logical, but filmography info seems large, so i edited mdb file, deleted Filmography2 field under People table, compacted and DB became 481 MB which is totally acceptable and faster. I kindly request an instruction about how to disable updating filmography info at IMDB script or it could be removed for the sake of everyone, as someone suggested XMM8 is not IMDB |
|
|
JDommi
Administrator
Germany
4657 Posts |
Posted - 27 Feb 2015 : 23:50:00
|
I would disable all #ADDFILMOGRAPHY# commands in the scripts. Or the better way is to add an option if the filmo should be taken or not. That needs at least 5 lines of code: one for the variable to take the yes/no option and the variable for and at the beginning of the filmo an #IF# block with a #GOTO# command. And of cource the label to go to when filmo should not be taken. By the way all movie scripts have their own oftion which fields to take. So IMDB(complete) don't need to be processed and the IMDB(fastest) doesn't have the filmo block for standard. |
In order to achieve what is possible, you have to try the impossible over and over again. Hermann Hesse |
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 28 Feb 2015 : 00:01:34
|
I am using only IMDB(complete), i hope you did not expect me to fix it by myself since i am not a developer :) |
|
|
JDommi
Administrator
Germany
4657 Posts |
Posted - 28 Feb 2015 : 00:41:00
|
I'm only a user, too
I just have had a look at the script. The Filmography can't be diabled by the fields option. For that I was wrong. But test this script: http://www.mediafire.com/view/jz66mkxir76hjhc/IMDB.COM_(Complete).txt Now there is another option (at the end) where you can check if the filmo should be taken. I didn't have tested the mod - so if there is an error please let me know. |
In order to achieve what is possible, you have to try the impossible over and over again. Hermann Hesse |
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 28 Feb 2015 : 08:40:40
|
Well let's say i am close to null about development since tried to figure out script file for some other problem for a long time but no progress :) It seems it's working, thank you very much for your help.
|
|
|
JDommi
Administrator
Germany
4657 Posts |
Posted - 28 Feb 2015 : 09:08:39
|
You're welcome! |
In order to achieve what is possible, you have to try the impossible over and over again. Hermann Hesse |
|
|
Topic |
|
|