Session trace not cleaned up causing "tracing.stop" error in subsequent tests with Playwright

从 session() 辅助函数和 Playwright trace 生命周期开始，使用复现的 session_test.js 场景以及启用 trace 和 keepTraceForPassedTests 的配置。按顺序运行两个场景，并在会话上下文关闭后跟踪清理过程。完成标准是复现过程在没有 tracing.stop 错误的情况下完成，并且 trace 处理仍然正确。

What are you trying to achieve?

I'm trying to run multiple test scenarios where the first scenario uses session() with Playwright helper and trace enabled. Both tests should pass without errors.

What do you get instead?

After the second test completes successfully, CodeceptJS throws an error:

Error: tracing.stop: Target page, context or browser has been closed

The session created in the first test is not properly cleaned up, and when the second test finishes, CodeceptJS attempts to save the trace for the old session that no longer exists.

Provide console output if related. Use --verbose mode for more details.

Session Bug Reproduction --
D:\projects\codeceptjs-bug\session_test.js
  First test with session
  Scenario()
    I am on page "/"
    user1: I am on page "/"
    user1: I see "Example Domain"
    I see "Example Domain"
  ✓ OK in 4197ms

  Second test - should fail with trace error
  Scenario()
    I am on page "/"
    I see "Example Domain"
  ✓ OK in 630ms

Error: tracing.stop: Target page, context or browser has been closed

  OK  | 2 passed   // 6s

Provide test source code if related

Feature('Session Bug Reproduction');

Scenario('First test with session', ({ I }) => {
  I.amOnPage('/');
  
  session('user1', () => {
    I.amOnPage('/');
    I.see('Example Domain');
  });
  
  I.see('Example Domain');
});

Scenario('Second test - should fail with trace error', ({ I }) => {
  I.amOnPage('/');
  I.see('Example Domain');
});

Details

• CodeceptJS version: 3.7.6
• NodeJS Version: v20+ (any recent version)
• Operating System: Windows / Linux / macOS (reproduced on all)
• Playwright version: 1.40.0
• Configuration file:

exports.config = {
  tests: './*_test.js',
  output: './output',
  helpers: {
    Playwright: {
      url: 'https://example.com',
      show: false,
      browser: 'chromium',
      trace: true,
      keepTraceForPassedTests: true
    }
  },
  bootstrap: null,
  mocha: {},
  name: 'codeceptjs-session-bug'
}

Additional context

The issue appears when:

• Multiple scenarios are run in sequence
• Trace is enabled (especially with keepTraceForPassedTests: true)
• One or more scenarios use session() helper

The session context is closed after the first scenario ends, but CodeceptJS still tries to stop tracing for it when the next scenario completes.

Minimal reproduction repository available if needed.