memory leak

[ebr 16170]

Does it come back down when the scan is over?

[wraslor 70]

No it stays high, even if I kill the process.

[ebr 16170]

No it stays high, even if I kill the process.

 

How can our use of memory stay high if you kill our process?

[Della Dog 19]

How can our use of memory stay high if you kill our process?

Current process (task maybe) not killing children?

http://stackoverflow.com/questions/3342941/kill-child-process-when-parent-process-is-killed

Edited October 29, 2013 by pdcinc

[Luke 42077]

An application releasing memory, and the operating system putting it back into the available pool are two completely separate events.

[wraslor 70]

I'm having an issue with the server when it runs the media scan.  I usually sit around 2-3gb of memory in use and I see MB just start sky rocketing all the way to just under my system ram of 16gb.

 

Right now for example it's scanning and I'm showing just under 9 gigs in use, granted in task manager mb server app shows 1,307,992k (highest memory use by far of anything else) and climbing steadily.  I can run the computer for days without mb server running and it will sit at 2-3gb depending on what's going on but once I run mb server and it kicks off a scan memory utilization starts climbing to the roof. 

 

Any ideas?  What would be the best way to log this to give you guys more information?

 

 

[Luke 42077]

this affects a small number of people. one of the next two server releases will bring our memory usage down.

[ebr 16170]

Yeah, the system only goes to re-claim memory when it needs to so watching task manager isn't always accurate.

 

But, I was confused by the statement of "it stays high" when you kill our process.

 

1) what is "it" because if we are gone, we wouldn't display in task manager for you to see any memory associated with us

2) when you say "kill the process" do you mean actually kill it in task manager?  Why would you do that as opposed to just shutting down the server?

[wraslor 70]

by it stays high I mean that in task manager the memory usage stays close to max and will drop slightly when I kill the process in task manager.  IE using 14gb of memory, kill process now using 13.8.  Same story if i just exit the server app.  The only time i've seen behavior like this is from a memory leak thus the OS not reclaiming the memory and it showing in use.

 

Let me know if I can get you any more information.

[haikuginger 0]

I'm posting to let you know that I'm having a similar issue. Immediately on boot, my system ramps up to using around 8GB of 12GB, as compared to 2-3GB typically. Killing the MediaBrowser.ServerApplication.exe process doesn't clear up the space, but I tried pulling the MB3 Server file from my startup folder, and on the next boot, my computer hovered around 2.5GB of memory usage. Opening up the server shortcut immediately started a quick ramp up to 7GB of total memory usage.

Edited November 11, 2013 by haikuginger

[Jimmy 12]

What is the normal usage of MediaBrowser.ServerApplication.exe in taskbar?

[ebr 16170]

What is the normal usage of MediaBrowser.ServerApplication.exe in taskbar?

 

I don't think we can say what "normal" is as it will depend heavily on your environment.  Mine typically hovers around 300MB.

[Jimmy 12]

ebr, thanks for replying so fast, i'm asking because when servers starts and for a long time it sits around 620MB but some times and after several hours it drops around 270MB and i dont know what resourses loads that cause the 620MB and in opposite what happens and it drops in 270MB!

[NizZ8 3]

I'm getting similar issue but getting these about 1x a day or so and have to restart MBServer.

 

-----------------

 

[Window Title]

Microsoft Windows

 

[Main Instruction]

Close programs to prevent information loss

 

[Content]

Your computer is low on memory. Save your files and close these programs:

 

Media Browser Server

 

 

[Close program] [Cancel]

 

[Footer]

Windows will only close enough programs to restore needed memory.

 

------------

 

I haven't been able to catch it when it hits this point, but once this fires it locks MBServer and i have to restart MBServer manually.

 

System has 8GB of memory.

 

Plugins i'm running:

• CoverArt
• Rotten Tomatoes Reviews
• ServerWMC
• Trakt

Any ideas?

[ebr 16170]

Server log when this happens?

[NizZ8 3]

Here is the fault in the Application Log, which was logged at approx 1:32am

 

Faulting application name: MediaBrowser.ServerApplication.exe, version: 3.0.5135.31685, time stamp: 0x52e047da

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc000041d

Fault offset: 0x736d4f0d

Faulting process id: 0x9bc

Faulting application start time: 0x01cf2ba02e3f0f91

Faulting application path: C:\Users\n8\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe

Faulting module path: unknown

Report Id: 9bc2c094-987f-11e3-96e7-74d43502d8de

 

EventData XML

<EventData>

  <Data>MediaBrowser.ServerApplication.exe</Data> 

  <Data>3.0.5135.31685</Data> 

  <Data>52e047da</Data> 

  <Data>unknown</Data> 

  <Data>0.0.0.0</Data> 

  <Data>00000000</Data> 

  <Data>c000041d</Data> 

  <Data>736d4f0d</Data> 

  <Data>9bc</Data> 

  <Data>01cf2ba02e3f0f91</Data> 

  <Data>C:\Users\n8\AppData\Roaming\MediaBrowser-Server\System\MediaBrowser.ServerApplication.exe</Data> 

  <Data>unknown</Data> 

  <Data>9bc2c094-987f-11e3-96e7-74d43502d8de</Data> 

  </EventData>

 

------------

 

The last few entries in the MBServer log were logged about ~10 minutes earlier:

 

2014-02-18 01:23:11.4651 Debug - ProviderManager: Running ProgramImageProvider

2014-02-18 01:23:11.4651 Debug - ProviderManager: Running ProgramImageProvider

2014-02-18 01:23:11.4821 Info - App: Refresh Guide Completed after 0 minute(s) and 49 seconds

2014-02-18 01:23:11.6101 Info - App: Sending web socket message ScheduledTaskEnded

 

Edited February 18, 2014 by NizZ8