OBJMTLLoader make web browser died when it deal with too much data

[BruceYong]

Mrdoob,I like your Three.js very much,but I got some problem recently.when I load a '.obj' and a '.mtl' by using OBJMTLLoader,I find that my browser looks like died.
Then I read your source,I'm sure that the network is ok(because we us async ajax),but by the time of callbackinng OBJMTLLoader's load,it invok parse function,right?Ok,the problem is that my *.obj get 114175 lines,it's too much,so the browser take a long time to parse it,the resualt is:browser looks like died!
I have thought out lots of ways,but no use.I even try to use nodejs,parse the data in servers,But the Engine don't support Float32Arry(sadly).
so,what do you think about this problem?thanks for reply!

[mrdoob]

The OBJMTLLoader isn't too optimal currently...
Do you mind trying the OBJLoader in the dev branch?

[BruceYong]

yeah,I will try,and I'm wondering if I can optimise it,thanks for reply,and I will connect you as soon as i find a way to optimise OBJMTLLoader!

[matthias77]

Hi there, I had the same problem. I've identified the mergeVertices function as the problem. I have commented it out for the moment and now it works much faster. I'm sure this is a useful function, but it solves my problem for the moment.

matt