Opened 6 years ago

Last modified 18 months ago

#14485 new bug

TextSearch crash

Reported by: khallebal Owned by: phoudoin
Priority: normal Milestone: Unscheduled
Component: Applications/TextSearch Version: R1/Development
Keywords: win32 prefix Cc:
Blocked By: #14345 Blocking:
Platform: x86

Description

searching for the words "win32" or "prefix" is enough to trigger the crash, 100% reproducible

Attachments (1)

TextSearch-4757-debug-13-09-2018-19-10-04.report (49.7 KB ) - added by khallebal 6 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by phoudoin, 4 years ago

Could you give more info on what was the searched folder content? Because, no, searching for win32 or prefix on any kind of folder content don't trigger a crash 100% of time. Or I really miss something on this issue report.

comment:2 by phoudoin, 18 months ago

Blocked By: 14345 added

comment:3 by phoudoin, 18 months ago

Seems similar to #14345, aka parsing grep output lines issue in Grepper::_RunnerThread() leading to segfault, or to segfault when adding brokenly extracted info to a BMessage::AddString()

Last edited 18 months ago by phoudoin (previous) (diff)

in reply to:  3 comment:4 by bipolar, 18 months ago

I can reliably crash TextSearch when searching for "syslog" on a local clone of Haiku's website.

Specifically, when searching under: /content/documents/dev/. I've managed to narrow it down to ONE file: system_logging.html.

Seems that the problem arises for files containing REALLY long lines.

I'm very bad using the Debugger, but the crash report for a debug build of TextSearch points at _IO_vscanf, so I assume it crashes on Grepper.cpp's line 419.

BTW, searching on that particular file crashes only on 32 bits. On 64, it works just fine.

Last edited 18 months ago by bipolar (previous) (diff)

comment:5 by bipolar, 18 months ago

BTW, khallebal's original report show the same type of error as mine "Exception (Segment violation)", and so it does the one from #17011 (al three from 32 bits).

Unlike Kapix's #14345, where the error is: "Exception (General protection fault)", and happens on 64 bits.

Maybe this one and #17011 are duplicates of the same bug?

Note: See TracTickets for help on using tickets.