メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

MediaProIC.log file grows without bounds

jsbraby
I've just started using Media Pro 1.4.2 to catalog my image archives and I have discovered that is has a very poor behavior. The MediaProIC.log grows ridiculously large. Over the last 12 hours while cataloging 11,000 images (217GB of media as reported by Media Pro), the MediaProIC.log has grown to 289 GB. It seems to be an infinite repeating series of messages like:

2014-07-02 07:21:43> (ERROR) MemJpeg error: Not a JPEG file: starts with 0xd9 0xff
2014-07-02 07:21:43> (ERROR) MemJpeg error: Unsupported marker type 0xff

This is either a bug, or the logging level is set inappropriately on this version of Media Pro. I've already deleted the MediaProIC.log once, but it continues to grow to silly proportions.

Is there a way to disable system logging in Media Pro? Or do I need to keep manually deleting a log file that in 12 hours grows larger than the actual sum of the media I am trying to catalog?

My system:
MacPro 3,1 Dual 2.8GHz
16 GB RAM
Mac OS X 10.9.3
Media Pro 1.4.2
Media being cataloged:
Canon EOS 5d Mark II .CR2 files
Canon EOS 5d Mark III .CR2 files
Canon EOS 5d Mark II .jpg files
Canon EOS 5d Mark III .jpg files
Canon EOS 7d .CR2 files
Canon EOS 7d .jpg files

Thanks for your help.
0

コメント

18件のコメント

日付 投票
  • H. Cremers
    I don't know where it comes from or how to change/solve it, but i had the same issue.

    Although not as big as your MediaProIC.log file, mine was some 90GB and that on an SSD of 120GB. So, system in panic, no more space left.

    Cost me 3 days and an app purchase (WhatSize at , recommended) to find out this file was the culprit. I can't think of anything i've done out of the ordinary that should have caused the application to write such a big log file.

    Looks to me like some developer forgot to turn off a bug trace or something like that.

    I didn't bother to log a support case, as i'm on my way out.

    This is with MP 1.4.2 on a Mac Pro 5.1 6-core, 48Gb and 120GB SSD, OSX 10.9.3 at the time.
    0
  • NNN635400101660476374
    I have the same problem and I have sent it to the Support.

    My solution in the moment is - delete version 1.4.2 and work with the older 1.4.1 what runs fine.
    0
  • bnes
    Same issue here.
    +1 on the WhatSize app for finding the out of control log file on a Mac.
    0
  • rainerfrey
    According to the messages in the first posts, it seems to be malformed JPEG files in the import sources.
    0
  • NNN635400101660476374
    Response from the Support:

    The Log file notes that their is 1 or more corrupt files that Media Pro continues to try to read.
    As long as these files exist, Media Pro will issue a Log entry to note the error in reading them and that certainly grow depending on how many corrupt images are present and how large the catalog is. This is, unfortunately, correct behavior given the right circumstances.


    ok. Only - with the same Fotos I have no problems in LR 3,4,5 no problems in Aperture and no problems in MP 1.4.1....

    Then a Logfile was growing as long as the harddisc is completly full - for me is not acceptable.
    0
  • H. Cremers
    Well, if they think that is correct behaviour, their system architect must have very different ideas to mine. I happen to design systems as well (not graphical, but business systems) and i would certainly allow at least for a configuration option to stop the repeated mentioning of the same error.

    I would say, if the error is considered so bad to mention it each time at the cost of many gigabytes, then make a pop-up out of it and make the user decide about the file.

    Anyway, as stated before, this is not my cup of tea, so i'm heading another way.
    0
  • NNN634452465601459995
    Hello
    just wanted my (iMac i7 32 GB + ext.) Thunderboltplatte) who see MediaProIC.log - can find anything but on the computer - and believe me I've found until now, if it was there.
    Can you tell me where is this log file???
    Thank you
    0
  • H. Cremers
    [quote="NNN634452465601459995" wrote:
    ... Can you tell me where is this log file???
    Thank you


    Yes, i can. It took me also some time to figure this out, as it is carefully hidden. The file is in:
    /Users/[youruser]/Library/Logs/MediaProIC.log
    0
  • NNN634452465601459995
    There are 5 of small logs, but nothing by MediaPro. My system is Mavericks 10.9.4-
    the Gallery is located at the images on ext. Plate and is at 2500000! Images just about 21 GB times the size. Got only MediaPro - no CaptureOne. There is this folder I do not--nowhere. Funny???
    0
  • NNN634452465601459995
    Sorry,
    noch mal auf deutsch : diesen Ordner MediaProIC.log gibt es auf meinem Computer nicht - nirgends
    und MediaPro läuft und läuft und läuft.
    0
  • H. Cremers
    Then nothing is wrong probably, i don't even read the logs. Why should i? they're so hidden, even more experienced users weren't aware of them.

    So, i don't know why someone is getting this file (it's really small for me now as well), but fact is some do and it can grow really, really big.
    0
  • NNN634452465601459995
    What happens if you she simply deleted??? Make backup before please !!!!can delete his - I sometimes delete with CCleaner and iTweaX - it the log files.
    "Log Files can be removed without risk" stands for iTweaX
    0
  • H. Cremers
    [quote="NNN634452465601459995" wrote:
    What happens if you she simply deleted??? ...


    I did, nothing happens, other than that my system returned to normal operation (startup disk was full due to big log file).

    In my humble opinion, it is not the smartest thing in the world to write a log file and let it get this big, without the user knowing and without possibility to change any setting about it, like disk to write it to.

    Further, in my opinion, an application log file should never be able to jeopardize the operation of an OS.
    0
  • NNN634452465601459995
    Unfortunately I know now no Council - especially I do not understand there is no file with me and with them already.
    Last catalogue approach - secure - MediaPro delete (AppCleaner.app) - perform cleaning (iTweaX) - computer new start - log file if still present delete - computer restart settings in MP noble - MediaPro re-download / install - refresh images - and I hope they have a praying the metadata into the images always

    I would like help - maybe someone knows otherwise still a Council

    Good luck
    0
  • H. Cremers
    [quote="NNN634452465601459995" wrote:
    ...

    I would like help - maybe someone knows otherwise still a Council

    Good luck


    Thanks ! But i am fine now.

    I am no longer using Media Pro and it is going well.
    0
  • NNN635400101660476374
    Thanks ! But i am fine now.

    I am no longer using Media Pro and it is going well.


    Thanks, my words too.
    0
  • rainerfrey
    [quote="NNN635400101660476374" wrote:
    Response from the Support:
    The Log file notes that their is 1 or more corrupt files that Media Pro continues to try to read.
    As long as these files exist, Media Pro will issue a Log entry to note the error in reading them and that certainly grow depending on how many corrupt images are present and how large the catalog is. This is, unfortunately, correct behavior given the right circumstances.

    ok. Only - with the same Fotos I have no problems in LR 3,4,5 no problems in Aperture and no problems in MP 1.4.1....

    Same old story as always: what to do when reading crappy data?
    It's either strictly complain, in order to get the producing programs to get it right. Uncanny for those who need to deal with the complaints.

    Or silently ignore it as long as you can get anything out of it somehow. Like Internet Explorer Quirks Mode. No matter how wrong the HTML is, display it as well as you can. Seems to be friendlier on first sight, but encourages the producing programs to not take care to get it right because "it works anyways".

    Seems like MP 1.4.2 chose the first way. For better or for worse. Can't blame them for wanting to do that.
    0
  • petervd81
    I'm experiencing the same, have asked support about it but I'm afraid I get the same answer.
    I don't get it?! There's only images in these folders, never had any problems with it.

    If this can't be fixed I can't work with MP!!
    Googling on this only brings me to this topic, are there really that few people that encounter this?
    0

投稿コメントは受け付けていません。