KiCad 8 crashes immediately

KiCad crashes while starting. I’m on a M1 MacBookAir:


Translated Report (Full Report Below)

Process: kicad [1757]
Path: /Applications/KiCad/KiCad.app/Contents/MacOS/kicad
Identifier: org.kicad.kicad
Version: 8.0.0 (8.0.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 503

Date/Time: 2024-02-26 09:33:45.4432 +0100
OS Version: macOS 14.3.1 (23D60)
Report Version: 12
Anonymous UUID: A81A461B-63B8-E637-EE1F-B9D3A61D7A23

Time Awake Since Boot: 3600 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 0xffffffffffffffef
Exception Codes: 0x0000000000000001, 0xffffffffffffffef

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1757]

VM Region Info: 0xffffffffffffffef is not in any region.
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
UNUSED SPACE AT END

Any help?

Kind regards, Wolfgang

Wenn du schon ein GitLab-Ticket erstellt hast, verlinke es. Ansonsten verschwenden andere ihre Zeit damit zu suchen.


(edit)
If you’ve already created a GitLab ticket, please link it here. Otherwise, people will have a hard time searching for it.

Hallo - die Tickets sind leider abgewiesen ( :stop_sign: This issue is missing the required full version information.). Mit der Begründung, dass eine korrekte Versionsangabe fehlt. Ich habe dann gemäß Anweisung “build-error” eingefügt; hat auch nicht geholfen. Insofern existieren die Tickets nicht - oder?


(edit)
Hello, the tickets were automatically closed with the reason that the correct version information was missing. I then entered the suggested “build-error” but that didn’t help.

In any case, the tickets still exist, correct?

Richtig, vielleicht diese Post kann dir helfen:


(edit)
Correct, maybe these posts can help you

Es ist ja durchaus richtig dieses Problem im Forum zu posten. Aber wie gesagt: Ein Link wäre hilfreich (ob geschlossen oder offen, du kannst ja das Problem des automatischen schliessen erwähnen).

Dieses Ticket wird bei mir als offen angezeigt.

Als Workaround musst du wohl vorläufig weiter mit KiCad 7.0 arbeiten.


(edit)
Posting to the forum is a good idea. However, as mentioned, it would be a good idea to post a link whether open or closed. The issue of automatic closing can be separately addressed.

This ticket looks open to me.

One workaround would be to continue using KiCad 7.0


Ansonsten wäre es interessant welche Versionen es genau betrifft:
Passiert dasselbe in 8.0.0-rc1? (Wenn nein, was ist mit 8.0.0-rc2 und 8.0.0-rc3 ?)
Läuft KiCad 7.0.11 ?
Die “alten” Versionen findest du Hier (macOS)

Ergebnisse direkt im existierenden Ticket posten.


(edit)
It would also be interesting to know which version this affects. Does it happen with 8.0.0-rc1? (If not, how about 8.0.0-rc2 or -rc3?)

Does KiCad 7.0.11 run?

You can find the older versions of KiCad to download here (macOS)

It would be useful to post your results directly in the ticket

Sorry - ich habe nur zweimal vom bot die Meldung bekommen, dass die Tickets geschlossen sind. Habe dann leider nicht weiter überprüft.

(edit) Sorry, the bot closed my tickets two times and I have not checked further as to why

I’m sorry but I don’t know what this thread is about, it sounds quite serious, is it please ?
:mouse:

About this problem KiCad 8.0.0 crashes immediately (#17122) · Issues · KiCad / KiCad Source Code / kicad · GitLab (KiCad crashes when starting)

OP had problems posting it on GitLab since he doesn’t have version info.

Please use English as per forum guidelines.

Wo genau finde ich diese “guidelines”?

(edit) Where exactly would I find these Guidelines?

Common sense should be enough.
Or you need to have rules, do you?

1 Like

I think this is a fair question. The answer is here: English is the language here

But the forum doesn’t have a great way to show a list of custom guidelines (as far as I know).

I will also point out that there are other forums that use non-English languages that might be easier than translating into English for some people.

For example Forum: Platinen - Mikrocontroller.net in German

Nun sind wir komplett vom Thema weg.

Wie du siehst sind sich die Moderatoren nicht einig.


(edit) Now topic is far away. - As you can see, the moderators do not agree.

My inclination is to let it go and see if a native speaker picks it up. My main concern is appropriate content but if I see a known member pick up the thread I don’t worry about it.


Common sense should be enough.

Gesunder Menschenverstand sagt mir keine Sprache zu schreiben die nicht gesprochen wird.


(edit) Common sense tells me not to write in a language that nobody speaks.

Or you need to have rules, do you?

Würde es eine Regel geben die mir vorschreiben in einer Sprache wie** Englisch zu schreiben würde ich nichts mehr Posten. Soll ich wirklich die Verbreitung einer so unsinnigen Sprache unterstützen?


(edit) If the rules say to only write in English, then I wouldn’t write anything. Should I really support the spread of such a language?

** Ich will jetzt nicht genau darauf eingehen warum Englisch noch unlogischer ist als andere Sprachen. Aber die sehr inkonsistente Aussprache der Buchstaben(-kombinationen) und Zahlen ab 1e9 als Beispiel sollten zur Illustration genügen.

** (edit) I won’t go into why English less logical than other languages. But the extremely inconsistent pronunciation of letters and numbers greater than 1e9 should suffice as examples.

The use of anything but English is hard work for us moderators, who have to keep an eye open for spamming or other abuse of the forum.

3 Likes

This discussion is no longer relevant to KiCad. Now going off-rails

Since the thread is closed I’ll leave the posts in tact.

But, yes, English is better for the most part here. Still, it isn’t mandatory if there is really a problem with translation.

1 Like

Not for me. (But I’m not a moderator).
When See something other then English, I usually just close the thread.

3 Likes