Segfault when calling Server#fetch with .routes

[jclem]

How can we reproduce the crash?

I'm trying to write tests using server.fetch(request). The server file only has this:

export const server = Bun.serve({
  routes: {
    "/": () => Response.json({ ok: true }),
  },

  port: process.env.PORT ?? 3000,
});

This segmentation fault happens when calling server.fetch(request).

Relevant log output

Stack Trace (bun.report)

Bun v1.2.5 (013fddd) on macos aarch64 [TestCommand]

Segmentation fault at address 0x00000000

• 1 unknown/js code
• DebugHTTPSServerPrototype__doFetch
• DebugHTTPSServerPrototype__doFetch
• WebCore::DebugHTTPServerPrototype__fetchCallback
• 1 unknown/js code
• jsc_llint_commonCallOp__llintOpWithMetadata__llintOpWithReturn__llintOp__commonOp__fn__fn__makeReturn__fn__fn__fn__666_callHelper__dispatch_LowLevelInterpreter64_asm_2535
• jsc_llint_commonCallOp__llintOpWithMetadata__llintOpWithReturn__llintOp__commonOp__fn__fn__makeReturn__fn__fn__fn__666_callHelper__dispatch_LowLevelInterpreter64_asm_2535
• jsc_llint_commonCallOp__llintOpWithMetadata__llintOpWithReturn__llintOp__commonOp__fn__fn__makeReturn__fn__fn__fn__684_callHelper__dispatch_LowLevelInterpreter64_asm_2535
• llint_call_javascript
• JSC::Interpreter::executeCall

Features: tsconfig, tsconfig_paths, http_server, jsc

_{Sentry Issue: BUN-D2G}

[jclem]

Ah, I think I misunderstood what server.fetch is used for!

[RiskyMH]

I'm not sure what .fetch does right now, but it shouldn't crash

[jclem]

I'm not sure what .fetch does right now, but it shouldn't crash

@RiskyMH I thought I could use it to test my server, which I've done in the past (I think?) when using Bun.serve({ fetch }). Looks like this happens when I'm using Bun.serve({ routes }), instead.

[alii]

Simple reproduction:

const s = Bun.serve({
  port: 3000,
  routes: {
    '/': new Response('Hey'),
  },
});

const res = await s.fetch('http://localhost:3000/'); // also fails using `/` as url
console.log(await res.text());