LgWebOs Plex App dies with message "App will now restart to free up more memory" streaming HDR

@Morphy & All.

Any captured player logs which caught the failure are always helpful.

Given the code for the LGs is the same for my C1 as any of the newer models, I suspect it’s the TV itself hogging more memory with all it’s loaded apps ( I had to trim them out of mine )

That aside, Logs will tell us what’s really happening and the team can look to see if any relief / better handling of low-memory condition can be achieved.

1 Like

@ChuckPa

Sounds good . I can send them tomorrow, where do you want the logs?

It kept dying today. Even deleted several apps, settings etc , spoke with LG and their ideas didnt work either .

I actually had Xplay on the old tv for backup , but I cant find it in the content store anymore .

I booted up my Apple 4K TV , it seems to be working just fine . But a bit “laggy” , seems that the refresh rate really cant keep up.

Few days ago got my Lg G5 and have the same problems . It’s drive me crazy and I have never seen on any other tv ! This is expensive junk tv

@ChuckPa , is there an official instruction set to follow to get logs from the LG TV Plex client app so that Owisun can also upload logs. Or do you think that we won’t/don’t need them?

Seeing when the TV app thinks it has to take action is important.

I’ve not been able to recreate it on my LG.

Setup to start logging.

https://support.plex.tv/articles/216955788-logging-for-smart-tvs-tivo/

When it next shows this error, do the second part of the above instructions to get the logs and then post here please

1 Like

I’ve just set up my G5 83 and am having the same free up memory issue whilst watching 4K content.

Im “happy” to see that im not the only one .

Still have the issue . Dont know how to fix this :frowning:

I have a QNED90 that is almost unwatchable with the built-in Plex app. The problem isn’t playback - that works fine. The problem is scrolling through libraries. It starts out fine but after two or three screens, gets slower and slower until it locks up completely. This doesn’t affect just the Plex app. The TV doesn’t respond to any remote buttons (Home. Off, etc.). Eventually I have to unplug the TV to get it to restart. Will see if I can capture anything in the log file.

There does not appear to be anything captured in the Media Server log.

Aug 19, 2025 09:21:07.003 [140365826607928] INFO - [Req#1c48d2] AutoUpdate: no updates available
Aug 19, 2025 09:21:08.268 [140365798841144] ERROR - [Req#1c48f8] Unknown metadata type: folder
Aug 19, 2025 09:21:08.269 [140365798841144] WARN - [Req#1c48f8] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.269 [140365798841144] WARN - [Req#1c48f8] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.276 [140365816646456] ERROR - [Req#1c48ea] Unknown metadata type: folder
Aug 19, 2025 09:21:08.276 [140365816646456] WARN - [Req#1c48ea] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.276 [140365816646456] WARN - [Req#1c48ea] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.276 [140365792602936] ERROR - [Req#1c48fd] Unknown metadata type: folder
Aug 19, 2025 09:21:08.277 [140365792602936] WARN - [Req#1c48fd] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.277 [140365792602936] WARN - [Req#1c48fd] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.279 [140365802298168] ERROR - [Req#1c48fe] Unknown metadata type: folder
Aug 19, 2025 09:21:08.279 [140365802298168] WARN - [Req#1c48fe] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.279 [140365823355704] ERROR - [Req#1c48ff] Unknown metadata type: folder
Aug 19, 2025 09:21:08.280 [140365802298168] WARN - [Req#1c48fe] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.280 [140365823355704] WARN - [Req#1c48ff] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.280 [140365823355704] WARN - [Req#1c48ff] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.286 [140365826607928] ERROR - [Req#1c4900] Unknown metadata type: folder
Aug 19, 2025 09:21:08.287 [140365826607928] WARN - [Req#1c4900] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:08.287 [140365826607928] WARN - [Req#1c4900] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:21:09.856 [140365798841144] ERROR - [Req#1c490e] Unknown metadata type: folder
Aug 19, 2025 09:21:09.863 [140365792602936] ERROR - [Req#1c490f] Unknown metadata type: folder
Aug 19, 2025 09:21:43.123 [140365802298168] INFO - Request: [192.168.1.60:57149 (Allowed Network (Subnet))] PUT /library/sections/1/all?type=1&id=193709&includeExternalMedia=1&collection.locked=1&collection%5B0%5D.tag.tag=Show%20Boat&collection%5B1%5D.tag.tag=Musicals (6 live) #1c49ea TLS GZIP Signed-in Token (xxxxxxxx)
Aug 19, 2025 09:21:43.208 [140366010678072] INFO - Completed: [192.168.1.60:57149] 200 PUT /library/sections/1/all?type=1&id=193709&includeExternalMedia=1&collection.locked=1&collection%5B0%5D.tag.tag=Show%20Boat&collection%5B1%5D.tag.tag=Musicals (6 live) #1c49ea TLS GZIP 84ms 325 bytes (pipelined: 13)
Aug 19, 2025 09:21:55.672 [140365823355704] INFO - Request: [192.168.1.60:57207 (Allowed Network (Subnet))] PUT /library/sections/1/all?type=1&id=193728&includeExternalMedia=1&collection.locked=1&collection%5B0%5D.tag.tag=Show%20Boat&collection%5B1%5D.tag.tag=Musicals (7 live) #1c4a0e TLS GZIP Signed-in Token (xxxxxxxx)
Aug 19, 2025 09:21:55.748 [140366008568632] INFO - Completed: [192.168.1.60:57207] 200 PUT /library/sections/1/all?type=1&id=193728&includeExternalMedia=1&collection.locked=1&collection%5B0%5D.tag.tag=Show%20Boat&collection%5B1%5D.tag.tag=Musicals (7 live) #1c4a0e TLS GZIP 75ms 325 bytes (pipelined: 8)
Aug 19, 2025 09:32:20.105 [140365823355704] INFO - [Req#1c4a64] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] [LogToPmsManager] Now logging to server
Aug 19, 2025 09:32:29.177 [140365823355704] INFO - [Req#1c4a68] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] [Server Retry] Starting connection retries to DS1621 (ready)
Aug 19, 2025 09:32:29.177 [140365823355704] INFO - [Req#1c4a68] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] [Server Retry] Retrying connection to DS1621 (ready)
Aug 19, 2025 09:32:34.571 [140365823355704] INFO - [Req#1c4a6b] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Clearing all screens!
Aug 19, 2025 09:32:34.571 [140365823355704] INFO - [Req#1c4a6b] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Navigating to screen: SourceTabbedScreen
Aug 19, 2025 09:32:34.571 [140365823355704] INFO - [Req#1c4a6b] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Navigated to screen: SourceTabbedScreen
Aug 19, 2025 09:32:34.571 [140365823355704] INFO - [Req#1c4a6b] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Clearing all screens!
Aug 19, 2025 09:32:34.571 [140365823355704] INFO - [Req#1c4a6b] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Navigating to screen: SourceTabbedScreen
Aug 19, 2025 09:32:34.571 [140365823355704] INFO - [Req#1c4a6b] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Navigated to screen: SourceTabbedScreen
Aug 19, 2025 09:33:01.666 [140365823355704] INFO - [Req#1c4a79] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] [Server Retry] Starting connection retries to DS1621 (ready)
Aug 19, 2025 09:33:01.666 [140365823355704] INFO - [Req#1c4a79] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] [Server Retry] Retrying connection to DS1621 (ready)
Aug 19, 2025 09:35:23.842 [140365823355704] INFO - [Req#1c4a83] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Opening modal: SettingsScreen
Aug 19, 2025 09:35:23.843 [140365823355704] INFO - [Req#1c4a83] [Plex for LG] [xxxxxxxx:29k32r0agphxzdfn0h5tick0] Opened modal: SettingsScreen
Aug 19, 2025 09:36:46.185 [140365792627512] INFO - [Req#1c4aa2] AutoUpdate: no updates available
Aug 19, 2025 09:36:47.327 [140365780446008] ERROR - [Req#1c4ac7] Unknown metadata type: folder
Aug 19, 2025 09:36:47.327 [140365780446008] WARN - [Req#1c4ac7] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.327 [140365780446008] WARN - [Req#1c4ac7] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.333 [140365767355192] ERROR - [Req#1c4aba] Unknown metadata type: folder
Aug 19, 2025 09:36:47.334 [140365778336568] ERROR - [Req#1c4ace] Unknown metadata type: folder
Aug 19, 2025 09:36:47.334 [140365767355192] WARN - [Req#1c4aba] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.334 [140365767355192] WARN - [Req#1c4aba] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.334 [140365778336568] WARN - [Req#1c4ace] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.334 [140365778336568] WARN - [Req#1c4ace] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.336 [140365823355704] ERROR - [Req#1c4acf] Unknown metadata type: folder
Aug 19, 2025 09:36:47.336 [140365792627512] ERROR - [Req#1c4ad0] Unknown metadata type: folder
Aug 19, 2025 09:36:47.337 [140365823355704] WARN - [Req#1c4acf] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.337 [140365792627512] WARN - [Req#1c4ad0] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.337 [140365823355704] WARN - [Req#1c4acf] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.337 [140365792627512] WARN - [Req#1c4ad0] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.338 [140365774039864] ERROR - [Req#1c4ad1] Unknown metadata type: folder
Aug 19, 2025 09:36:47.339 [140365774039864] WARN - [Req#1c4ad1] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:47.339 [140365774039864] WARN - [Req#1c4ad1] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Aug 19, 2025 09:36:58.800 [140365823355704] INFO - [Req#1c4b11] AutoUpdate: no updates available

I just got the LG G5 and this is also happening to me. I watch a few minutes and then the app crashes with the freeing up memory message. On average I get to watch only 4-5 minutes at a time. Plex menus during play are also very laggy and unresponsive.
I have already removed ALL other installed apps and even reset to factory settings AND removed all other installed apps again, no difference.

Really awful for a super expensive TV like this. I really hope this can be fixed soon.

@ChuckPa - Seems that several LG users are seeing the same issue that I have . Would really like to help but last time the logs didnt show anything :frowning: - even after a crash.

@Multiversus May I ask if you are using subs on your media? Because I posted in a PM to Chuck with a file that had too many subs within. Something like max was 28 for Samsung and LG and the file had.. like 31 ( OR something like that , cant remember entirely :slight_smile: ) .

But I see the issue with 1080p and 2160p as well.

Really annoying :frowning:

@Morphy

You’re correct, the maximum number of subtitle tracks most televisions can handle is 28 for Samsung and 32 for LG dependent on age & firmware.

Most BluRays have well over 30 subtitle tracks.

Some folks forget to skip/drop those unused / not needed tracks as they rip from the BluRay when remuxing to the output file which is usually a MKV file.

When they forget, those TVs with MKV capability are then forced to receive and strip the subtitles internally. This can lead to a lot of memory fragmentation and eventually running out of memory (too many small unusuable blocks).

For those cases where a single movie is identified as causing the app to restart (repeatedly), the first step is to count the number of subtitle tracks and work backward in time from there by examining the media info and counting.

@ChuckPa thanks for the reply .

But isn’t it odd that it happens on new LG models and not the older ones? Don’t have any issues on my older LG TV ( LG G1 )

@Morphy The last media that I was trying to watch and that was crashing the client continuously had 28 subtitles tracks. The crashing happened with or without subtitles enabled.

1 Like

@Multiversus any chance you might can send the file to @ChuckPa ? Can you enable logging in the app on the TV, and the server ?

He couldnt see any errors in mine , nor the file I had problems with .

Before sending the file to anyone, I recommend remuxing the file and removing all but the needed subtitle tracks.

Keep the original elsewhere for now.
Retest playback with the remuxed files.

We found 28 was the limit but that file had one video and two audio tracks for a total of 31 tracks.

31 might be the absolute limit for that TV’s firmware

From a practical sense, are 28 subtitle tracks really needed ?

Thanks for that confirmation , that some thing i have always done when checking the file. Strip out the subs that are not required.

MKVToolNix to the rescue again.

LG 65 “G4 OLED with a Apple TV on 2025.23

Awesome :ok_hand: @ChuckPa :wink:

Sortet out my Apple TV 4K with no stuttering (60hz) . Running smooooooothhhhh .

Plex on TV paused for now

Just set up my LG G5. Watched one 1080p movie. Plex restarted four times during the movie with this error. I’ve been using Plex for almost 20 years on a variety of devices and TVs. I’ve never seen anything like this.

I noticed that the Plex app hasn’t been updated for a year now. Surely there have been bug fixes since then? This is absolutely ridiculous. Plex lists the LG app first on their page of supported TVs. So, is LG supported or not? Because this is broken beyond belief. My Xbox runs Plex better than this. Plex on my Sony Android A95K was perfectly fine. I sold off my Apple TV thinking the TV would allow me to have one fewer devices to control.

Seeing Plex try to convince me to pay for plex pass when they don’t support the client is embarassing. I just read some posts from 2019 here that are complaining about this same issue. Is anyone at the wheel here?

1 Like

Im having the same Issue over here on a LG 65C5. My Phillips OLED 805 was running the App much more stable.

I was encountering random restarts of the App, without any Pop-Ups or anything.