Crash when clicking on options in … (More Options) popup in the Properties panel
This one exist for at least a year: when object is selected and Properties panel docked to the right, click on the … (More Options) button in the Transform section. Then it either crashes immediately or when some option is modified (like "Scale Strokes and Effects").
I remember I reported that while ago, but got no reply and obviously no attention from support team.
Top of the crash report:
Process: Adobe Illustrator [44604]
Path: /Applications/Adobe Illustrator 2024/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
Identifier: com.adobe.illustrator
Version: 28.3.0 (28.3.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2024-03-23 20:18:35.4441 +0200
OS Version: macOS 13.6.5 (22G621)
Report Version: 12
Anonymous UUID: 7ABCBAF3-9B93-72F9-4C87-153C354F26DA
Sleep/Wake UUID: 6FE71DB3-8669-425E-9C7F-EC00BE3DEEFF
Time Awake Since Boot: 380000 seconds
Time Since Wake: 1440 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [44604]
VM Region Info: 0 is not in any region. Bytes before following region: 4334239744
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 102574000-1039a8000 [ 20.2M] r-x/r-x SM=COW ...e Illustrator
Kernel Triage:
VM - (arg = 0x0) pmapenter retried due to resource shortage
VM - (arg = 0x0) pmapenter retried due to resource shortage
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 TransformPalett 0x13e3d6928 0x13e3c4000 + 76072
1 TransformPalett 0x13e3d4fec 0x13e3c4000 + 69612
2 TransformPalett 0x13e3e71b0 0x13e3c4000 + 143792
3 TransformPalett 0x13e3da9a0 0x13e3c4000 + 92576
4 TransformPalett 0x13e3cf194 0x13e3c4000 + 45460
5 TransformPalett 0x13e3d0c4c 0x13e3c4000 + 52300
6 TransformPalett 0x13e3cf80c 0x13e3c4000 + 47116
7 dvaui 0x106b78220 0x106b04000 + 475680
8 dvaui 0x106b76a70 0x106b04000 + 469616
9 dvaui 0x106b775b4 dvaui::controls::UIInteractiveControlView::FinishInteractiveChange() + 48
10 dvaui 0x106c64a64 dvaui::controls::UITextEdit::TextMessageNotify(dvaui::controls::TextEditAction, dvaui::controls::OSEditText*) + 388
11 dvaui 0x106be5928 dvaui::controls::UINumberEdit::TextMessageNotify(dvaui::controls::TextEditAction, dvaui::controls::OSEditText*) + 24
12 dvaui 0x106b3550c dvaui::controls::OSEditText::SendTextEditAction(dvaui::controls::TextEditAction) + 168
13 dvaui 0x106b2c6e4 dvaui::controls::OSEditTextItemMAC::UIFocusChanged(dvaui::ui::FocusChangeReason) + 128
14 dvaui 0x106e4fac8 dvaui::ui::UINode::UIDispatchFocusChange(std::1::list<boost::intrusiveptr<dvaui::ui::UINode>, std::1::allocator<boost::intrusiveptr<dvaui::ui::UINode>>> const&, dvaui::ui::FocusChangeReason) + 76
15 dvaui 0x106e4fcf8 dvaui::ui::UINode::UIUpdateKeyboardFocusStateDueToLoss() + 192
16 dvaui 0x106e6bd14 dvaui::ui::UIDialog::UIActivationChanged(dvaui::ui::UINode::WindowActivation) + 28
17 dvacore 0x104bc6a24 0x104b6c000 + 371236
18 Adobe Illustrator 0x102b509d8 0x102574000 + 6146520
19 dvacore 0x104bc691c dvacore::config::ExecuteTopLevelFunction(std::__1::function<void ()>, bool*) + 92
Yury
shared this idea
-
I made a simplified repro video:
It crashed even without group/enter the group part, but I cannot repro it in a stable way.
-
Hi Egor,
I am not sure I reported this issue before with the forum, it probably was just filling the crash form. Should be either my gmail address or yar @ fontlab.com, but that doesn't really matter as it crashes in the latest build.
Do you want me to share my AI preferences file?
Best regards,
Yury -
Yury, hi!
Thanks for the report (and FontLab). I checked UserVoice for older reports about this and found nothing. Perhaps the report had been made at forums or through PR program?
Anyway, it behaves OK for me, but on Windows. I will try to ask someone to test it using the same configuration as you have.
Do you use the same email to file the crash report as you use here at UV?
