Yes, this is a known issue. There is progress on the browser side to more efficiently handle such large programs, but no browser does this well yet.
Emscripten supports dynamic linking, https://github.com/kripken/emscripten/wiki/Linking This can be a solution for this problem, by splitting things up into smaller files. In practice, personally, I tend to use print debugging and I open the file in a text editor on the side that can handle massive text files. On Fri, Dec 4, 2015 at 12:02 PM, arnab choudhury <[email protected]> wrote: > Hey all > > I'm using Emscripten to convert a decent sized C++ codebase to Javascript. > As part of this process, I'm finding that debugging the unoptimized > generated JS can be quite painful. Specifically, some JS files can be up to > 1 million lines long and this completely breaks my browser's node debugger > (via node-inspector). Google's v8 debugger (via node debug) also has a hard > time stepping through code. My only debugging technique that works > currently is to enter print statements, and debug and build iteratively. > > I saw some threads on github about emscripten having the ability to split > up the generated JS files into multiple files. However, the latest version > of emscripten doesn't seem to support this. Have others run into this > issue? Are there any existing solutions for this problem? > > Thanks, > Arnab > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
