[fixed] MP2 Importer Exception of type 'System.OutOfMemoryException' was thrown. (3 Viewers)

[henso]

Will this be a general change for everybody?

AFAIK OpenCV is also using ffmpeg but is 2-10 times faster. At least it was when I tested it last. Did the change to ffmpeg help anything or was it any of all other changes done?

 

[Terra]

Did the change to ffmpeg help anything or was it any of all other changes done?

Sorry I cannot answer that, I applied all changes mentioned in the thread step by step to solve the issue, not sure which change was the most relevant one.

 

[morpheus_xx]

Did the change to ffmpeg help anything or was it any of all other changes done?

It was a try to see if out-of-process thumb creation works better, but I think it did not make the relevant change, as we have seen OOM after replacement as well.

 

[sridharb]

Hi,

I am also getting similar OOM errors. I notice that you were fixing it. Do you have a version that I could try?

Thanks,
Sridhar

[2019-01-18 00:18:09,793] [8286521] [28 ] [INFO ] - TvdbHandler: Loading series 73314
[2019-01-18 00:19:54,589] [8391317] [77 ] [INFO ] - TvdbHandler: Loading series 77526
[2019-01-18 00:20:03,210] [8399938] [98 ] [INFO ] - TvdbHandler: Loading series 71040
[2019-01-18 00:22:57,586] [8574314] [98 ] [INFO ] - TvdbHandler: Loading series 76290
[2019-01-18 00:23:15,521] [8592249] [112 ] [ERROR] - Unable to query
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Text.StringBuilder.ToString()
at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
at MediaPortal.Backend.Services.MediaLibrary.MIA_Management.GetMIAAttributeColumnName(AttributeSpecification spec)
at MediaPortal.Backend.Services.MediaLibrary.QueryEngine.BaseQueryBuilder.RequestSimpleAttribute(QueryAttribute queryAttribute, IDictionary`2 tableQueries, IList`1 tableJoins, String miaJoinType, IDictionary`2 requestedAttributes, IDictionary`2 miaTypeTableQueries, RequestedAttribute miaIdAttribute, RequestedAttribute& requestedAttribute)
at MediaPortal.Backend.Services.MediaLibrary.QueryEngine.MainQueryBuilder.GenerateSqlStatement(Boolean groupByValues, IDictionary`2 miamAliases, String& mediaItemIdOrGroupSizeAlias, IDictionary`2& attributeAliases, String& statementStr, IList`1& bindVars)
at MediaPortal.Backend.Services.MediaLibrary.QueryEngine.CompiledMediaItemQuery.GetMediaItems(ISQLDatabase database, ITransaction transaction, Boolean singleMode, IEnumerable`1 selectedMIAs, IList`1& mediaItemIds, IDictionary`2& complexMediaItems, Boolean forceSingleMIAMode)
at MediaPortal.Backend.Services.MediaLibrary.QueryEngine.CompiledMediaItemQuery.Query(ISQLDatabase database, ITransaction transaction, Boolean singleMode)
[2019-01-18 00:23:20,535] [8597263] [28 ] [WARN ] - Request not successful for retrieve series details for 76290

 

[HTPCSourcer]

Do you have a version that I could try?

You may want to read through the thread. Most recent patch can be found in posting #17.

 

[sridharb]

Thanks, I did. However, it looks like the developer still is working on the issue (or related issues). My question was whether he was done and has a "official" patch that he has checked in.

 

[HTPCSourcer]

This is the final status. If you want it to be more official, you’ll need to wait until we release the next version.

 

[sridharb]

Something is/seems wrong with the FanArt changes. It is stuck like

[2019-01-20 13:25:58,721] [18816974] [103 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 13:26:00,351] [18818604] [118 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 13:26:08,706] [18826959] [113 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 13:26:11,622] [18829875] [95 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.

[2019-01-20 16:09:32,731] [28630984] [112 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 16:09:35,090] [28633343] [112 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 16:10:43,708] [28701961] [107 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 16:10:47,666] [28705919] [112 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.
[2019-01-20 16:10:51,205] [28709458] [112 ] [INFO ] - FanArtActionBlock: Persisting 99141 fanart actions.

Notice the break in time and there is no movement.

 

[sridharb]

More to the point, I had triggered an import of my Movie folder this morning after putting in place the new files. It progressed to about 6% by around 0830 (a few minutes after I had started) and then there has been no progress since then. There is CPU and disk activity throughout, but no progress other than these log items above. What exactly is happening and where do I look?

Update: after reverting to the 2.2 versions of the files and retriggering an import, it reaches 48% and seems stuck, but CPU and disk usage much lower than before. I also don't see the persistent FanArt actions as before. However, the last messages in the log is:


[2019-01-20 16:52:46,645] [1193791] [98 ] [INFO ] - ImporterWorker.ImportJob(#1).DirectoryUnfoldBlock: Successfully processed 5666 MediaItems; time elapsed: 00:18:08.6092793; MaxDegreeOfParallelism(InnerBlock) = 1
[2019-01-20 16:52:46,646] [1193792] [89 ] [INFO ] - ImporterWorker.ImportJob(#1).DirectorySaveBlock: Successfully processed 5666 MediaItems; time elapsed: 00:18:08.5089175; MaxDegreeOfParallelism(InnerBlock) = 1
[2019-01-20 16:52:46,730] [1193876] [87 ] [INFO ] - ImporterWorker.ImportJob(#1).FileUnfoldBlock: Successfully processed 50884 MediaItems; time elapsed: 00:18:08.4293517; MaxDegreeOfParallelism(InnerBlock) = 1

If it is "finished" why is the status in the settings shown as 48%

The last entry is

[2019-01-20 16:49:41,615] [1008761] [110 ] [INFO ] - ImporterWorker: 49 % completed (1 ImportJob(s), in total 4700 of 9654 so far identified resources processed)

The entries of "ImporterWorker" successfully processed comes soon after this 49% completed. As I said, the settings page still displays 48% complete.

Memory usage is high (910M), but no OOM errors