镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Large strings decoded from latin1 and then encoded to utf8 has wrong size #22728

Description

@henrik-ep
  • Version: v8.11.4
  • Platform: Linux xyz 4.17.5-200.fc28.x86_64 deps: update openssl to 1.0.1j #1 SMP Tue Jul 10 13:39:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  • Subsystem:

Decoding a latin1 buffer larger than about 1MB to a string and encoding that string into utf-8 gives a buffer with the same number of bytes as the latin1 input even though more are required for characters that use more space in utf-8.

This seems to work properly on v10.x but not v8.x or v9.x.

Code that demonstrates the problem:

const fs = require('fs');
const s = 'Räksmörgås';
let ss = '';

const SIZE = (1024 * 1024);
// works:
//const SIZE = (1024 * 512);

while (ss.length < SIZE) {
    ss = ss + ss.length + ' ' + s + '\n';
}

// create latin1 buffer we can decode
let l1Buffer = Buffer.from(ss, 'latin1');
let l1String = l1Buffer.toString('latin1')
// also fixes it:
// l1String = ('x' + l1String).substring(1, l1String.length + 1);
// create utf8 buffer from decoded latin1 string
let u8Buffer = Buffer.from(l1String, 'utf8')

console.log(l1Buffer.length);
console.log(u8Buffer.length);

if (l1Buffer.length === u8Buffer.length) {
    console.log('failed, should be different size');
} else {
    console.log('works');
}

Activity

  1. jasnell commented on Sep 6, 2018

    @jasnell
    Member

    Quick test on 8.11.4 confirms the difference in behavior between Node.js 8 and 10.

    /cc @nodejs/intl @nodejs/buffer @srl295

  2. added
    bufferIssues and PRs related to the buffer subsystem.
    on Sep 6, 2018
  3. added
    encodingIssues and PRs related to the TextEncoder and TextDecoder APIs.
    on Sep 6, 2018
  4. addaleax commented on Sep 6, 2018

    @addaleax
    Member

    This was fixed by #18216, I think.

  5. jasnell commented on Sep 6, 2018

    @jasnell
    Member

    Yep, makes sense. That PR is still pending a backport to 8.x. Once the backport happens, this issue should be resolved.

  6. addaleax commented on Sep 6, 2018

    @addaleax
    Member

    → Backport is in #22731

  7. starkwang commented on Nov 14, 2018

    @starkwang
    Contributor

    This issue is fixed in #18216 and #22731 so I'd like to close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bufferIssues and PRs related to the buffer subsystem.confirmed-bugIssues and PRs for confirmed bugs.encodingIssues and PRs related to the TextEncoder and TextDecoder APIs.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions