Björn Ritzl

> Next step is to change how the buffer save and load buffer is created to allow serialization of larger tables. I'm thinking that it might make sense to dynamically...

``` editor.debugging.mobdebug$connect_BANG_$fn__43465.invoke.class clojure.lang.ExceptionInfo: Failed to connect to debugger on localhost:8172 at editor.debugging.mobdebug$connect_BANG_$fn.invoke(mobdebug.clj:341) at clojure.lang.AFn.run(AFn.java:22) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.lang.Thread.run(Thread.java:829) ```

@PrashantVaingankar Does this happen all the time?

Tarantool uses a forked LuaJIT version. The memory profiler is taken from LuaVela: https://github.com/luavela/luavela/blob/master/src/profile/uj_memprof.c I'm skeptical about maintaining our own fork with a memory profiler included. I would much rather...

It might be possible to create our own memory profiler using a custom allocator: http://www.lua.org/manual/5.1/manual.html#lua_setallocf

> for example using > https://github.com/pmusa/lmprof This requires Lua 5.2 or newer

Do we need to copy the fields (ie both key and value) from the extension game.project file or would it be enough to define which keys that should be present...

Perhaps the process can be automated further? What if we always copy any game.project fields from the extension where the section matches the extension name as defined in ext.manifest? For...

Ok, well, that's definitely more advanced use cases which I didn't consider. Ok, then your approach is probably better.

Thanks! We will review this feature request and get back to you here.