BUG: pd.read_csv crashes when CSV contains "2e06918610327a" in version 2.3.3 #62881
Description
Pandas version checks
-
I have checked that this issue has not already been reported.
-
I have confirmed this bug exists on the latest version of pandas.
-
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
with open('test.csv', 'w') as f:
f.write('id\n2e06918610327a\n')
import pandas as pd
df = pd.read_csv('test.csv', engine='c')Issue Description
The reproducible example will give a segfault.
This bug exists on the latest version 2.3.3, but does not exist on 2.3.2.
engine='python' also has this issue.
Expected Behavior
Not crash can load the CSV correctly
Installed Versions
INSTALLED VERSIONS
commit : 9c8bc3e
python : 3.10.13
python-bits : 64
OS : Linux
OS-release : 6.14.0-33-generic
Version : #33~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 19 17:02:30 UTC 2
machine : x86_64
processor : x86_64
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : en_US.UTF-8
pandas : 2.3.3
numpy : 1.26.4
pytz : 2025.2
dateutil : 2.9.0.post0
pip : 25.1.1
Cython : None
sphinx : None
IPython : 8.37.0
adbc-driver-postgresql: None
adbc-driver-sqlite : None
bs4 : None
blosc : None
bottleneck : None
dataframe-api-compat : None
fastparquet : None
fsspec : None
html5lib : None
hypothesis : None
gcsfs : None
jinja2 : 3.1.6
lxml.etree : None
matplotlib : 3.10.3
numba : 0.61.2
numexpr : None
odfpy : None
openpyxl : 3.1.5
pandas_gbq : None
psycopg2 : None
pymysql : None
pyarrow : 20.0.0
pyreadstat : None
pytest : None
python-calamine : None
pyxlsb : None
s3fs : None
scipy : 1.15.3
sqlalchemy : None
tables : None
tabulate : None
xarray : None
xlrd : None
xlsxwriter : None
zstandard : None
tzdata : 2025.2
qtpy : None
pyqt5 : None