Core dump crash

[jakeleventhal]

• Version: v12.9.0
• Platform: Linux b8b01391ee38 4.9.125-linuxkit deps: update openssl to 1.0.1j #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 GNU/Linux
• Subsystem: Running on the node:latest docker image

Please see the issue here googleapis/nodejs-firestore#739
This describes details of how I was able to reproduce this problem using the @google-cloud/firestore module.
Regardless of the module, node should not be crashing like this.

[Trott]

@nodejs/http2

[addaleax]

@jakeleventhal Thanks for the report! Any chance you could share reproduction code? It may seem like “nothing complicated” to you or other people familiar with the firestore module, but it would be very helpful to have something a bit more concrete.

[jakeleventhal]

Here is the function that is being ran (I changed some variable names and removed some intermediate steps that are just manipulating variables - nothing that has to do with promises or networking). From the looks of it, there is nothing inconspicuous going on here

export const saveReportData = async (cateogories, reportData) => {
    // Create the map of updates
    const allUpdates = {};
    cateogories.forEach((category) => {
      allUpdates[category] = { items: {} };
    });
  
    await Promise.all(
      reportData
        .filter(
          ({ channel }) => cateogories.includes(channel)
        )
        .map(
          async ({
            id,
            email,
          }) => {
            // Get the existing item
            const existingItem = await firestore.doc(`Items/${id}`).get();
  
            // If the item is already saved in the database and hasn't been processed yet
            if (existingItem.exists && !existingItem.data().Processed) {
              const itemUpdatePayload = {
                Processed: true,
                User: email,
                Status: 'Complete'
              };
  
              // Update the item in the database
              await firestore.doc(`Items/${id}`).update(itemUpdatePayload);
            }
          }
        )
    );
  };

[addaleax]

Unfortunately, I can’t reproduce an error with that code (ran it with dummy input saveReportData(['a', 'b', 'c'], [{ channel: 'a', id: 'foo', email: 'bar' }])).

We could just remove that check, but this does point to a bigger bug in the HTTP/2 implementation of some kind, and so it would be really good to figure out what that is.

[jakeleventhal]

Like i said in the other issue, I can’t get it to reliably reproduce. In fact it’s the minority of cases. And it appears to always happen after a deadline exceeded error.

on a side note, how are these deadline exceeded errors avoided anyway

[addaleax]

on a side note, how are these deadline exceeded errors avoided anyway

I’m afraid that’s a question for the GCP folks.

[cjihrig]

on a side note, how are these deadline exceeded errors avoided anyway

I’m afraid that’s a question for the GCP folks.

To clarify that a bit more, the deadline is a gRPC specific concept - you can see the stack trace contains @grpc/grpc-js.

[jakeleventhal]

Okay, well if it isn’t going to break anything, can the check be removed? At least until the source of the problem is found

[addaleax]

#29399 should fix this.

[jakeleventhal]

#29399 should fix this.

Hopefully. How long does it take for node to release updates though...?
I am using the official node:latest docker image. Should I expect months of wait time before this gets resolved and is verified?

[bnoordhuis]

@jakeleventhal For latest probably 1-2 weeks.

[danbriggs5]

Could this also be affecting older versions? Seeing something similar on v10.16. If so, how long would it take to get a fix released to 10.16?

[jakeleventhal]

@addaleax is there any validation plan for this? I am unable to reliably produce the error

[bnoordhuis]

@danbriggs5 #29202 (comment) :-)