QGIS closes when additional column added to an attribute table for a layer

[amj1711]

What is the bug or the crash?

I am adding a column to a vector layer attribute table, called TITLE REF, set as text and 20 characters. When clicking okay QGIS immediately shuts down.

I then get the Apple, your program closed down unexpectedly and gives the following information;

---

Translated Report (Full Report Below)

Process: QGIS [32315] Path: /Applications/QGIS-LTR.app/Contents/MacOS/QGIS Identifier: org.qgis.qgis3 Version: 3.34.11 (3.34.11 ()) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501

Date/Time: 2024-09-23 15:00:08.3792 +0100 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Bridge OS Version: 8.6 (21P6074) Anonymous UUID: E8FD65C6-FBA0-E3F1-FA0E-2135D83FB1B8

Sleep/Wake UUID: 3C910DEB-7091-4D32-9F2B-1E9D981DE73A

Time Awake Since Boot: 35000 seconds Time Since Wake: 9102 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Codes: 0x0000000000000001, 0x0000000000000008

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: QGIS [32315]

VM Region Info: 0x8 is not in any region. Bytes before following region: 4481605624 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START --->
__TEXT 10b1fe000-10b266000 [ 416K] r-x/r-x SM=COW /Applications/QGIS-LTR.app/Contents/MacOS/QGIS

Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

Steps to reproduce the issue

Open an attribute table Select Edit Add a column Click Okay

Versions

QGIS Version: 3.34.11 (3.34.11 ()) OS Version: macOS 14.6.1 (23G93)

Supported QGIS version

• [X] I'm running a supported QGIS version according to the roadmap.

New profile

• [ ] I tried with a new QGIS profile

Additional context

No response

[Ipickedausername]

I have the same crashes, I think. When adding / removing a column (even when selecting a field in the attribute form after changing the default value of another field).

But I have never been able to reproduce these crashes. It seems random.

I hope your issue will help !

[agiudiceandrea]

@Ipickedausername, what is the exact QGIS version are you using and on which Operative System?

[jgrocha]

Hi @amj1711, what kind of vector layer provider are you using? Geopackage? Shapefile? Postgresql? Virtual layer?

[amj1711]

Shapefile. ThanksAlexSent from my iPhoneOn 24 Sep 2024, at 21:24, Jorge Gustavo Rocha @.***> wrote: Hi @amj1711, what kind of vector layer provider are you using? Geopackage? Shapefile? Postgresql? Virtual layer?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[jgrocha]

Not able to reproduce the error with the current master.

I've created a new shapefile, then I added the new column. No problem.

I've edited the shapefile and added two points.

Then I added another field. No problem.

@amj1711 Where is your shapefile? Can you check if you have permission to read/write the shapefile (and the folder where it is)?

[Ipickedausername]

@agiudiceandrea I'm working on this version 3.36.1-Maidenhead ; using Windows 10. I cannot try another version for now, as long as I don't have a proper internet access.. But I don't want to change the topic of this issue. If I find a way to reproduce the issue, I will open another issue.

[github-actions[bot]]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue. In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue. If there is no further activity on this issue, it will be closed in a week.