tsMuxeR GUI eats all available RAM

[toddvj]

I am running Windows Vista x64 with 8GB of RAM. Previously, I ran XP with 4BG ram and didn't have this problem:

When I run tsMuxeR (or TsRemux) to demux or rebuild BD-R file structure, it often maxes out my ram, and locks up the computer almost completely. I can sit and watch the memory usage go up and up as the program runs. I'm sure this is due to Vista (or the 64 bit version, anyway), but does anyone have any tips to get around this? One of the main reasons I wanted to run the x64 version is so that I could use more RAM.

For encoding, this machine is twice as fast as my XP machine, but for the simple tasks, it takes forever.

Thanks.

[ocgw]

I am running Windows Vista x64 with 8GB of RAM. Previously, I ran XP with 4BG ram and didn't have this problem:

When I run tsMuxeR (or TsRemux) to demux or rebuild BD-R file structure, it often maxes out my ram, and locks up the computer almost completely. I can sit and watch the memory usage go up and up as the program runs. I'm sure this is due to Vista (or the 64 bit version, anyway), but does anyone have any tips to get around this? One of the main reasons I wanted to run the x64 version is so that I could use more RAM.

For encoding, this machine is twice as fast as my XP machine, but for the simple tasks, it takes forever.

Thanks.

I have a Windows 7 RC x64 build 7100/8GB HTPC and use TsMuxer and can assure you that this not normal behavior, you need to repair or reinstall your OS

ocgw

peace

[toddvj]

Any reason why you jump straight to the Operating System? Most of the hardware is new, too. Believe me, I'd rather it be a simple matter of re-installing, but I'd like to know for sure, because "a simple matter of re-installing" often ends up being a 2or 3 day project

[ocgw]

Any reason why you jump straight to the Operating System? Most of the hardware is new, too. Believe me, I'd rather it be a simple matter of re-installing, but I'd like to know for sure, because "a simple matter of re-installing" often ends up being a 2or 3 day project

Most of the hardware is new?, well that does change things bro', how long ago did you last install new hardware, if this symptom started right after a hardware upgrade, by all means uninstall that hardware in device manager and see

Sounds like you just built this PC, or just upgraded the OS, is this correct?

Give us all the details and somebody here will probably be able to help you

Anyway what you are experiencing sounds like a "memory leak", memory leaks are caused by poorly coded software, TsMuxer doesn't rely on any third party software to operate, just the OS, hence w/o any other info to go on I immediately suspect your OS, did you just happen to try out some new software recently?

ocgw

peace

[ocgw]

pls delete

ocgw

peace[/quote]

[toddvj]

For all intents and purposes, this is a new computer. I used my old Processor (Q6600), hard drives (Seagate 750GB x 2), BD-R drive (LG GGW-H20L) and Video Card (Radeon HD3870) but am using a new motherborard, RAM, case and power supply. The main reason for this build was to get better performance with Blu-Ray authoring/burning.

As far as installing any new software, I guess you could say it's all new. It's all stuff I've used before, though (except the OS). The only time I've had this problem with the memory was when I was using either TsRemux or tsMuxer. I've had the problem several times. Sometimes rebooting the computer helps.

Since I posted my first post, I haven't had it happen again, so it's kinda hard to troubleshoot. It's just the worry every time I fire up the program that it might happen again. I know that's not very helpful.

I'll post here if it happens again, and try to nail down what the problem is. I'm pretty good at troubleshooting, but sometimes it helps to have another set of eyes.

[redwudz]

I haven't noticed that problem, but I use Vista 32. And I do have a 3870 video card, but it probably doesn't have anything to do with the problem. I have 4GB RAM and haven't noticed tsMuxeR using any unusual amount of RAM. It could be a OS problem, but I'm not sure how to check that.

Visa and W7 have some system diagnostics in the form of Task Manager and the Event Viewer and maybe the Memory Diagnostics Tool. Look in Control Panel>Administrative Tools and see if there are some clues there.

Memory leaks sound like a possibility. (Basically using RAM for one purpose and not releasing it for others) http://en.wikipedia.org/wiki/Memory_leak

[toddvj]

Good tips. I'll have to wait for it to happen again, though.

[ocgw]

I haven't noticed that problem, but I use Vista 32. And I do have a 3870 video card, but it probably doesn't have anything to do with the problem. I have 4GB RAM and haven't noticed tsMuxeR using any unusual amount of RAM. It could be a OS problem, but I'm not sure how to check that.

Visa and W7 have some system diagnostics in the form of Task Manager and the Event Viewer and maybe the Memory Diagnostics Tool. Look in Control Panel>Administrative Tools and see if there are some clues there.

Memory leaks sound like a possibility. (Basically using RAM for one purpose and not releasing it for others) http://en.wikipedia.org/wiki/Memory_leak

Yeah redwudz has the right idea, when it happens again I would go to task manager and go to the processes tab and you may see what is eating up all your resources

ocgw

peace

[doctorcd]

Hi Guys,

Exact same promlem here. I am running Vista x 64 with 8GB RAM. Same problem occurs when using other programs like MakeMKV, Ripbot264, MKV2VOB but suspect only when the dexumxin stage of execution is being carried out.

Looking at the Processes and mem usage in Task manager seems to show no culprit that I can identify.

As soon as the demuxing starts, memory usage rises linearly , when it hits max, the computer slows to a crawl.

Several others seem to have had this problem as I have found from a google but I guess it is just not common enough to have raised enough interest.

Any ideas welcome.

[Revlisx]

I'm also having exactly the same problems on some files using MKV2VOB, when checking task manager it shows that TxMuxer is indeed the culprit.

Running Vista x64 with 6GB RAM.

I hope someone can help.

[Baldrick]

Have you tried run tsmuxer standalone and demux/mux the files?

If that also cause same problem try contact the tsmuxer author, http://www.smlabs.net/tsmuxer_en.html . Be sure to include as much information as possible.

[doctorcd]

Hi Baldrick.

Yes indeed it occurs using TSmuxer standalone.

However as Revlisk has pointed out, it occurs only on some backup rips only, and not others. For that reason I expect this problem will be a tough one to identify.

Is there any other program out there that can demux an mt2s file that I can try, to see if the problem does in fact lie with the source file and not the demux program or operating system ?

Thanks in advance.

[Revlisx]

Have you tried run tsmuxer standalone and demux/mux the files?

If that also cause same problem try contact the tsmuxer author, http://www.smlabs.net/tsmuxer_en.html . Be sure to include as much information as possible.

Yes i have also tried to run tsmuxer on it's own to no avail, it is such a shame because i use this everyday and now some files cannot be muxed because of this memory issue.

Little extra info :

If i do allow the muxing to continue after the memory reaches 99-100% it will eventually finish (although nothing else can be done whislt waiting) the resulting file with have audio sync problems

[Revlisx]

Just to update all with this issue, i did contact tsMuxeR and the reply was..

tsMuxeR uses maximum near 200-300 Mb memory. Possible problem with your system allocate all memory for file cache when tsMuxeR makes read/write disk operations.

Best regards,
Roman

Now as you can see this didn't really help my problem at all, HOWEVER i upgraded my os to windows 7 x64 and now the problem has completely gone, i'm not sure why but theres obviously some kind of problem with vista x64..hope this helps anyone who's having this same problem

EDIT: Unfortunately there is a downside, MKV2VOB runs much MUCH slower than it used to with xp (before all these problems) and don't think about uninstalling then re-installing..you will only get the same problem again (eating up too much ram) i did this and had to do a system restore to get it back and avoid the RAM problem , but like i said..it is much slower

[pepelugil]

I've just buyed a new PC with Windows 7 x64 Ultimate, and I'm having exactly the same problem with tsMuxeR

As soon as I start a Remux all RAM (6GB) starts que get used (but if you look at the processes running none of them is using the RAM ) and then the system gets completely unusable (even the remux process slows down)... This is doing the remux from one HDD to another, I'll make some more tests to see if I can isolate where the problem is.

[Revlisx]

Its interesting that quite a few people are having the same problems HOWEVER no-one seems to be complaining outside this thread, what i mean is i haven't seen anyone complain about similar problems anywhere and i've searched through google etc.

pepelugil Please do update us with your findings or if anyone has any information on this issue, posting it here would be a great help.

[Major Armstrong]

I have the same problem on my 8 GB computer, i use Win 7 Pro x64 right now.
I did not have that problem when using Vista Ultimate x64. It just fills the ram up in under a minute and sits there until im done remuxing. Seems really strange. I guess ill just have to use VmWare XP image to do this now also :P
Its pretty irritating anyways.
I hope someone find out where the problem lies. its beginning to be a problem for quite a few people now.

Major Armstrong

P.S. Im running it in XP Mode right now and theres no problem doing that. Just FYI It's irritating to have to do that, but thats the way it is, easier than restarting the computer between every mux.

[pepelugil]

Well, I've located (and then solved) where my problem is... It's really silly:

I had another program that had random accesses to the m2ts file I was demuxing, so Windows 7 was so "clever" that it tried to cache in my 6GB of RAM the 30GB mt2s that tsMuxeR was working with in order to "accelerate" the requests from the other program (which, yes it's uTorrent, and before anyone blames me, in my country that's still not warez, but it seems sadly that this will not last to long).

If I close uTorrent (or just stop this file) and do the remux with tsMuxeR everything goes fine... So, at least from my point of view, if you have a similar problem, just look if any other program is accessing to the file you are re/demuxing and stop it before using tsMuxeR.

Greetings

[Major Armstrong]

With my computer it's the system thats accessing the files at the same time, i really dont know why or even how to stop it. I dont even use uTorrent. Well ill just have to use the Virtual XP mode method for now.

[doctorcd]

Hey Pepelugil, smart work, you solved my problem thanks.

I run uTorrent and of course if its seeding the same file file you are trying to deMux then two programs will need to access the file at the same time. But I would have assumed that the operating system was smart enough not to escalate the memory usage to capacity and such and extreme so that the machine becomes inoperable. Thats why it did not even cross my mind.

Top work and well spotted.