message: fix crash caused by closing Lua too early

Pending messages may have `.free` callbacks pointing to functions in
loaded Lua C modules (DLL/SO). Closing Lua first invalidates these
pointers, so `message.free` may call an invalid function.

Author: findstr

lualib-src/lhive.c

@@ -215,7 +215,7 @@ static int l_worker_gc(lua_State *L)
 	struct worker *w = (struct worker *)lua_touserdata(L, 1);
 	if (unlikely(w->task_id != 0)) {
 		silly_log_warn("[hive] A worker was still busy during GC. This may cause a memory leak report on exit. "
-			"Check for blocking calls or infinite loops in hive tasks.");
+			"Check for blocking calls or infinite loops in hive tasks.\n");
 		// If the worker is still running in the thread pool,
 		// the only possible reason it was garbage collected is that its Lua state has been closed.
 		// In this case, we can rely on the process exit cleanup to handle it automatically.

silly-src/silly_worker.c

@@ -357,7 +357,7 @@ void silly_worker_warnendless()
 
 void silly_worker_exit()
 {
-	lua_close(W->L);
 	silly_queue_free(W->queue);
+	lua_close(W->L);
 	silly_free(W);
 }