Exception on captureException() call

[mark-b-ab]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/node

SDK Version

7.11.1

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

Catch exception, call captureException.

Expected Result

Exception being reported to Sentry

Actual Result

/home/node/node_modules/@sentry/utils/cjs/misc.js:25
    crypto && crypto.getRandomValues ? () => crypto.getRandomValues(new Uint8Array(1))[0] : () => Math.random() * 16;
                                                                                      ^

TypeError: Cannot read properties of undefined (reading '0')
    at /home/node/node_modules/@sentry/utils/cjs/misc.js:25:87
    at /home/node/node_modules/@sentry/utils/cjs/misc.js:30:19
    at String.replace (<anonymous>)
    at Object.uuid4 (/home/node/node_modules/@sentry/utils/cjs/misc.js:29:46)
    at Hub.captureException (/home/node/node_modules/@sentry/hub/cjs/hub.js:130:86)
    at /home/node/node_modules/@sentry/node/cjs/integrations/onuncaughtexception.js:71:17
    at Hub.withScope (/home/node/node_modules/@sentry/hub/cjs/hub.js:98:7)
    at OnUncaughtException.handler (/home/node/node_modules/@sentry/node/cjs/integrations/onuncaughtexception.js:69:15)
    at process.emit (node:events:525:35)
    at process.emit (node:domain:489:12)
    at process._fatalException (node:internal/process/execution:167:25)

[Lms24]

Hi @mark-b-ab thanks for reporting!

We recently made a change (#5426) to how we create uuids so this might have to something with your problem.

Could you tell us a little bit about your setup? For instance, it would be good to know the node version you're using? Also, are you using any frameworks (e.g. Express)? Can you provide a small reproduction what to do to get to this error?

[mark-b-ab]

I use node:18 container. NestJS as a framework. I can't send you code to reproduce as this error I receive if I have any unhandled exception in my app.

[mark-b-ab]

I added this code it try catch where I report exceptions

      try {
        const { crypto, msCrypto } = getGlobalObject();
        console.log('global.crypto || global.msCrypto', crypto, msCrypto);
      } catch (e) {
        console.log('global.crypto || global.msCrypto crashed', e);
      }

      try {
        const global = getGlobalObject();
        const crypto = global.crypto || global.msCrypto;

        console.log('randomUUID func', crypto.randomUUID);
        console.log('randomUUID called', crypto.randomUUID());
      } catch (e) {
        console.log('randomUUID crashed', e);
      }

      try {
        const global = getGlobalObject();
        const crypto = global.crypto || global.msCrypto;

        console.log('randomBytes func', crypto.randomBytes);
        console.log('randomBytes called', crypto.randomBytes());
      } catch (e) {
        console.log('randomBytes crashed', e);
      }

      try {
        const global = getGlobalObject();
        const crypto = global.crypto || global.msCrypto;

        console.log('getRandomValues func', crypto.getRandomValues);
        console.log('getRandomValues called', crypto.getRandomValues(new Uint8Array(1)));
      } catch (e) {
        console.log('getRandomValues crashed', e);
      }

      try {
        console.log('uuid4 func', uuid4);
        console.log('uuid4 called', uuid4());
      } catch (e) {
        console.log('uuid4 crashed', e);
      }

      try {
        console.log('crypto UUID func', randomUUID);
        console.log('crypto UUID called', randomUUID());
      } catch (e) {
        console.log('crypto UUID crashed', e);
      }

[mark-b-ab]

Here is result

global.crypto || global.msCrypto { getRandomValues: [Function: getRandomValues] } undefined
randomUUID func undefined
randomUUID crashed TypeError: crypto.randomUUID is not a function
    at KafkaConsumer.onBatch (/home/node/dist/apps/ethereum-indexer-sushiswap/main.js:1:181174)
    at async Runner.processEachBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:274:7)
    at async onBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:449:9)
    at async Runner.handleBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:461:5)
    at async /home/node/node_modules/kafkajs/src/consumer/worker.js:29:9
randomBytes func undefined
randomBytes crashed TypeError: crypto.randomBytes is not a function
    at KafkaConsumer.onBatch (/home/node/dist/apps/ethereum-indexer-sushiswap/main.js:1:181397)
    at async Runner.processEachBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:274:7)
    at async onBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:449:9)
    at async Runner.handleBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:461:5)
    at async /home/node/node_modules/kafkajs/src/consumer/worker.js:29:9
getRandomValues func [Function: getRandomValues]
getRandomValues called undefined
uuid4 func [Function: uuid4]
uuid4 crashed TypeError: Cannot read properties of undefined (reading '0')
    at /home/node/node_modules/@sentry/utils/cjs/misc.js:25:87
    at /home/node/node_modules/@sentry/utils/cjs/misc.js:30:19
    at String.replace (<anonymous>)
    at uuid4 (/home/node/node_modules/@sentry/utils/cjs/misc.js:29:46)
    at KafkaConsumer.onBatch (/home/node/dist/apps/ethereum-indexer-sushiswap/main.js:1:181783)
    at async Runner.processEachBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:274:7)
    at async onBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:449:9)
    at async Runner.handleBatch (/home/node/node_modules/kafkajs/src/consumer/runner.js:461:5)
    at async /home/node/node_modules/kafkajs/src/consumer/worker.js:29:9
crypto UUID func [Function: randomUUID]
crypto UUID called 7871dbb7-ccd7-4ca9-8a8e-4b6c33af6468

[mark-b-ab]

The last UUID is from node crypto module

[mark-b-ab]

Seems that Sentry SDK is not using NodeJS Crypto module but a polyfill

[lobsterkatie]

Hi, @mark-b-ab.

Thanks for doing that investigation! The results are puzzling, though:

• The global crypto object should only exist when running your node process with the --experimental-global-webcrypto flag. Are you? If not, I would not expect global.crypto to be defined at all, and yet for you it shows as { getRandomValues: [Function: getRandomValues] }.

• Given that global.crypto is there at all, though, I'd expect it to have randomUUID (added in node 16), since you say you're running your app in node 18.

• global.crypto does seem to have getRandomValues (as I would expect, since it was added in node 15), but for some reason it's returning undefined, which isn't listed in the docs as one of the possible return values.

• At the beginning of your test code, you call crypto.randomUUID and it's undefined. At the end, you call randomUUID (which you say is from crypto) and it's defined. I assume that's because in the latter case you're talking about actually having required/imported the built-in crypto module, rather than relying on the global version?

UPDATE: I did some experimenting on my own machine, with more confusing results. Specifically, while the node docs say that global.crypto should be different from the built-in crypto module, for me, both bare crypto and global.crypto give me the full crypto module, same as when I require('crypto'). (And no, I'm not running with the special flag I mentioned.) This happens in both node 14 and node 18.

In any case, my best guess is that maybe this has to do with the node binary you're using inside your container. Do you know anything about it other than its version?

Meanwhile, @timfish, since you worked on this - do you have any idea what's going on here? It all seems very strange...

[timfish]

Yeah very strange. The stack trace and results from that script don't add up in a way I can fathom. Would love to try out that container!

(And no, I'm not running with the special flag I mentioned.)

My testing showed that in node v18+ global.crypo.randomUUID() worked in official builds. I never did work out what was wrong with their docs!