[MDEV-14098] [Draft] InnoDB: Failing assertion: btr_pcur_restore_position(BTR_MODIFY_TREE, pcur, mtr) Created: 2017-10-20  Updated: 2023-09-24  Resolved: 2023-09-24

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Cannot Reproduce Votes: 0
Labels: None

Attachments: File master.err     File master.log     File trial3.log    

 Description   

http://buildbot.askmonty.org/buildbot/builders/qa-win-debug/builds/672/steps/crash_tests/logs/stdio

10.3 3722372ae56b7ea90ee3801889e9d4cd275cf3b9

2017-10-20 10:44:37 0x2590  InnoDB: Assertion failure in file D:\qa-win-debug\build\storage\innobase\row\row0upd.cc line 2882
InnoDB: Failing assertion: btr_pcur_restore_position(BTR_MODIFY_TREE, pcur, mtr)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
171020 13:44:38 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
 
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
 
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.
 
Server version: 10.3.3-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=7
max_threads=65537
thread_count=12
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4240 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0xaab4d1ca38
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_sigabrt_handler()[my_thr_init.c:488]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:71]
mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:62]
mysqld.exe!row_upd_clust_rec()[row0upd.cc:2882]
mysqld.exe!row_upd_clust_step()[row0upd.cc:3184]
mysqld.exe!row_upd()[row0upd.cc:3278]
mysqld.exe!row_upd_step()[row0upd.cc:3422]
mysqld.exe!row_update_for_mysql()[row0mysql.cc:1951]
mysqld.exe!ha_innobase::update_row()[ha_innodb.cc:9130]
mysqld.exe!handler::ha_update_row()[handler.cc:6054]
mysqld.exe!mysql_update()[sql_update.cc:811]
mysqld.exe!mysql_execute_command()[sql_parse.cc:4530]
mysqld.exe!mysql_parse()[sql_parse.cc:7921]
mysqld.exe!dispatch_command()[sql_parse.cc:1821]
mysqld.exe!do_command()[sql_parse.cc:1369]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:366]
mysqld.exe!tp_callback()[threadpool_common.cc:192]
mysqld.exe!tp_callback()[threadpool_win.cc:378]
mysqld.exe!work_callback()[threadpool_win.cc:452]
ntdll.dll!RtlFreeUnicodeString()
ntdll.dll!RtlFreeUnicodeString()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xaab4d46090): UPDATE t1 SET col3 = NULL LIMIT 2  /* QNO 1640 CON_ID 21 */
Connection ID (thread ID): 21
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_grouping_derived=on

E:\buildbot\rqg/runall.pl --no-mask --seed=1508496021 --threads=5 --duration=400 --queries=100M --reporters=QueryTimeout,Backtrace,ErrorLog,Deadlock,Shutdown --redefine=conf/mariadb/redefine_random_keys.yy --redefine=conf/mariadb/redefine_set_session_vars.yy --validators=TransformerNoComparator --transformers=ConvertSubqueriesToViews,DisableOptimizations,EnableOptimizations,ExecuteAsCTE,ExecuteAsInsertSelect,ExecuteAsPreparedOnce,ExecuteAsSelectItem,ExecuteAsUnion,ExecuteAsUpdateDelete,ExecuteAsView,NullIf,OrderBy,StraightJoin,ExecuteAsExecuteImmediate --grammar=conf/runtime/alter_online.yy --gendata=conf/runtime/alter_online.zz --mtr-build-thread=150 --basedir1=D:\qa-win-debug\build --vardir1=E:\buildbot\vardirs\qa-win-debug\10.3-672\optim-crash-tests/current1_1

Not easily reproducible.



 Comments   
Comment by Elena Stepanova [ 2017-12-29 ]

https://api.travis-ci.org/v3/job/322918422/log.txt

Comment by Marko Mäkelä [ 2018-02-21 ]

This could be a duplicate of MDEV-14837 if the grammar included ADD COLUMN.

Comment by Elena Stepanova [ 2023-09-24 ]

It did include ADD COLUMN.

Generated at Thu Feb 08 08:10:54 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.