[SERVER-44617] $regexFind crash when one of the capture group doesn't match the input but pattern matches Created: 14/Nov/19  Updated: 29/Oct/23  Resolved: 28/Nov/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 4.2.1
Fix Version/s: 4.2.2, 4.3.3

Type: Bug Priority: Critical - P2
Reporter: Alex Bevilacqua Assignee: Arun Banala
Resolution: Fixed Votes: 0
Labels: qexec-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-13253 Investigate changes in SERVER-44617: ... Closed
Duplicate
is duplicated by SERVER-44929 Assert Location51156 faired in $regex... Closed
Problem/Incident
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Query 2019-12-02
Participants:
Case:

 Description   

When running a simple regex query against 4.2.1 the mongod will crash with:

2019-11-14T05:52:41.884-0500 F  -        [conn1] terminate() called. An exception is active; attempting to gather more information
2019-11-14T05:52:41.982-0500 F  -        [conn1] std::exception::what(): out of range



 Comments   
Comment by Githook User [ 28/Nov/19 ]

Author:

{'name': 'Arun Banala', 'username': 'banarun', 'email': 'arun.banala@10gen.com'}

Message: SERVER-44617 $regexFind crash when one of the capture group doesn't match the input but pattern matches
(cherry picked from commit 294ff7c1f6a3f79342aace87be524532d222da9f)
Branch: v4.2
https://github.com/mongodb/mongo/commit/66334e9063743d14a309ab645d8c1b6b0fd95771

Comment by Githook User [ 28/Nov/19 ]

Author:

{'name': 'Arun Banala', 'username': 'banarun', 'email': 'arun.banala@10gen.com'}

Message: SERVER-44617 $regexFind crash when one of the capture group doesn't match the input but pattern matches
Branch: master
https://github.com/mongodb/mongo/commit/3db0d100d3eef85a060cf3f69fc3e6a5c3f37cd6

Comment by Carl Champain (Inactive) [ 15/Nov/19 ]

Passing this ticket along to the Query team.

Generated at Thu Feb 08 05:06:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.