Report bug: Go To ... (CTRL-G) causes multiple "Bad allocation" dialogs

  • I have an XML document (13,614 lines) that I am trying to import into an application. There are character set errors that I need to resolve, and the errors are shown by the importing app as a line number. If i use the Go To … dialog to traverse to the line in question, I get multiple “Bad allocation” dialogs show.

    I am using Notepad++ 7.5.9 Build time: Oct 14 2018 - 15:02:52

  • This FAQ shows where to go to report a bug.

    In 7.5.8 and 7.6.3 (32bit or 64bit), I can make a 70k line XML (<tag>something here</tag> x 70000 lines) and successfully use Ctrl-G GoTo to get to any line in that file I want.

    You have not really given enough information to be able to replicate the problem. For reporting the version, make sure you include all of ? > Debug Info > Copy debug info into clipboard. Also, giving a minimal test case like I did: you don’t have to give your proprietary information, or paste the whole file. But doing something like I did above, or like

      <tag2 with=attributes>
        Content goes here

    and saying “repeat that 3000 times” – assuming those 15000 lines were enough to reliably replicate your problem, that’s sufficient.

    If doing something like that is not sufficient to replicate your problem, you’ve actually given yourself good debug information: perhaps it’s in the complexity of the nesting, or something. Maybe you’ve got invalid/malformed XML, and something in the lexer/parser is failing (you might want to try an XML validator, like perhaps the XML Tools plugin; since you’re in 7.5.9, you could just use the Plugin Manager to install XML Tools).

    If you give us more information, we may be able to help you figure out what’s going wrong, but right now, we cannot do much but guess. There may be nothing we can do – it may require a fix in the software – but if we can replicate it, it will give you more information to include in your bug report, which will give it a better chance of being solved.

  • Also, since both this forum and the official issues tracker use Markdown, the links in the following paragraph will help you include sample data like I did, so that the forum Markdown engine doesn’t mangle your data by interpreting its special characters as Markdown:

    This forum is formatted using Markdown, with a help link buried on the little grey ? in the COMPOSE window/pane when writing your post. For more about how to use Markdown in this forum, please see @Scott-Sumner’s post in the “how to markdown code on this forum” topic, and my updates near the end. It is very important that you use these formatting tips – using single backtick marks around small snippets, and using code-quoting for pasting multiple lines from your example data files – because otherwise, the forum will change normal quotes ("") to curly “smart” quotes (“”), will change hyphens to dashes, will sometimes hide asterisks (or if your text is c:\folder\*.txt, it will show up as c:\folder*.txt, missing the backslash). If you want to clearly communicate your text data to us, you need to properly format it.

Log in to reply