Log from the bottom of fml-client-latest.log:

http://pastebin.com/3xj2iSX3

I'm running on Linux 64bit with 8GB ram.
Whenever I join my server or my single player world, it goes up to max ram.

I have allocated 1GB, but yet it goes up to 6-7GB of RAM, and my computer freezes.

It happened right after I installed the latest version of Buildcraft.

Could this be a memory leak, perhaps?

Using 1.7.10

not seeing anything BC related at all in that log, only openblocks errors

Edit:

You're right.
However, it may be an incompability with OpenBlocks perhaps?

Also, if I remove Buildcraft from my mods, everything is just fine...
So its def. buildcraft related.

@AEnterprise could that happen because of the Difference with the Forge API because it seems to be that happens because of the fluids.... Maybe Openblocks has still the old API and bc has the new one... Just thinking

@Speiger i don't think so, it is possible they didn't update but i would expect it to crash then, eighter way it shouldn't be BC related as BC has nothing to do with openblocks, they don't have any specific integration

It probable that is from forge fluid registering change.

plus fluxgoo is from mod called thaumcraft. i would try to update forge and thaumcraft and OpenBlocks seen if that change

@AEmterprise
it is sure that it is a Openblocks bug, but BC causes it to happen. That is a fact!
Maybe @Asie should talk to the Openblocks guys and solve the problem.

i think it should be reproted at the openblocks dev, they obviously have a check with warning build so they should be able to tell us what the exact problem and possible causes are

My words xD Sorry for misstyping your name, Phone Keys are so small xD

Pinging @boq and @mikeemoo here

Hi,

Just to clarify:

• OpenBlocks uses only parts of pipe API - and they are fetched from Maven repo. So this is unrelated
• This warning occurs when FluidRegistry.getFluidStack(fluid.getName(), ...) returns null. Since we are iterating over FluidRegistry.getRegisteredFluids(), it looks like registration error
• I'm not sure who owns liquids fluidpure, fluiddeath and fluxgoo, but it's probably not BC
• if you can't find original mod author and make him fix his fluid registration, you can disable this part of code with config option displayAllFluids.
• Try updating Forge. There were big changes with fluid registering few months ago.
• Unless you have memory snapshot from profiler, I'm not investigating any reports about memory leaks - there are just too many false ones. Sorry.

That sounds more like Thaumcraft but he is right^^"