Segmentation fault when fill all

Bug #1845576 reported by lê văn lập
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Committed
Critical
Unassigned

Bug Description

affter add a filled zone, press B (fill all),software exit all with error segmentation fault

Application: Pcbnew
Version: 5.99.0-unknown, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.65.3 OpenSSL/1.1.1c (Schannel) zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.39.2
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.65.3
    Compiler: GCC 9.2.0 with C++ ABI 1013

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Tags: pcbnew
Revision history for this message
Seth Hillbrand (sethh) wrote :

Please attach the board for which this happens.

Changed in kicad:
status: New → Incomplete
Revision history for this message
lê văn lập (leevawns) wrote :
Revision history for this message
Ian McInerney (imcinerney) wrote :

I am unable to reproduce this with the attached board on my Linux master branch build, the zone fill doesn't crash.

Application: Pcbnew
Version: (5.99.0-165-g2e3d781bf), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.65.3 OpenSSL/1.1.1c-fips zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.9.0/openssl/zlib nghttp2/1.38.0
Platform: Linux 5.1.18-300.fc30.x86_64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.65.3
    Compiler: Clang 8.0.0 with C++ ABI 1002

Build settings:
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
    KICAD_STDLIB_DEBUG=OFF
    KICAD_STDLIB_LIGHT_DEBUG=OFF
    KICAD_SANITIZE=OFF

Revision history for this message
jean-pierre charras (jp-charras) wrote :

I also cannot reproduce the crash on W7 32bits.

Revision history for this message
Seth Hillbrand (sethh) wrote :

@leevawns- Can you find the segmentation fault line in you Windows Event Viewer and copy the text here to the report?

Revision history for this message
lê văn lập (leevawns) wrote :

Log Name: Application
Source: Application Error
Date: 27/09/2019 8:33:12 CH
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: RD-LAP
Description:
Faulting application name: kicad.exe, version: 0.0.0.0, time stamp: 0x5d8b1d5c
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x636bcb43
Exception code: 0xc0000005
Fault offset: 0x0003e87a
Faulting process id: 0x1f7c
Faulting application start time: 0x01d57537b5b8f804
Faulting application path: C:\msys32\mingw32\bin\kicad.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 0c108d3c-b09f-4806-b0ac-d08d72b79d83
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-27T13:33:12.983067500Z" />
    <EventRecordID>122471</EventRecordID>
    <Channel>Application</Channel>
    <Computer>RD-LAP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>kicad.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>5d8b1d5c</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.17134.799</Data>
    <Data>636bcb43</Data>
    <Data>c0000005</Data>
    <Data>0003e87a</Data>
    <Data>1f7c</Data>
    <Data>01d57537b5b8f804</Data>
    <Data>C:\msys32\mingw32\bin\kicad.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>0c108d3c-b09f-4806-b0ac-d08d72b79d83</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Revision history for this message
lê văn lập (leevawns) wrote :

Log Name: Application
Source: Windows Error Reporting
Date: 27/09/2019 8:33:18 CH
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: RD-LAP
Description:
Fault bucket 1746662657589397972, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: kicad.exe
P2: 0.0.0.0
P3: 5d8b1d5c
P4: ntdll.dll
P5: 10.0.17134.799
P6: 636bcb43
P7: c0000005
P8: 0003e87a
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER385A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43D4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4423.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4421.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4432.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_kicad.exe_46f7bb173c4d176eda1af82b6853cb1ab773411_9dfd6974_08914b07

Analysis symbol:
Rechecking for solution: 0
Report Id: 0c108d3c-b09f-4806-b0ac-d08d72b79d83
Report Status: 268435456
Hashed bucket: b1c9d20c82bd4790583d646ed00e49d4
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-27T13:33:18.210677000Z" />
    <EventRecordID>122472</EventRecordID>
    <Channel>Application</Channel>
    <Computer>RD-LAP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>1746662657589397972</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>kicad.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>5d8b1d5c</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.17134.799</Data>
    <Data>636bcb43</Data>
    <Data>c0000005</Data>
    <Data>0003e87a</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER385A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43D4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4423.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4421.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4432.tmp.txt</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_kicad.exe_46f7bb173c4d176eda1af82b6853cb1ab773411_9dfd6974_08914b07</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>0c108d3c-b09f-4806-b0ac-d08d72b79d83</Data>
    <Data>268435456</Data>
    <Data>b1c9d20c82bd4790583d646ed00e49d4</Data>
    <Data>0</Data>
  </EventData>
</Event>

Revision history for this message
Seth Hillbrand (sethh) wrote :

@leevawns- Can you download an official build from https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/nightly/ and see if it happens there also?

Revision history for this message
lê văn lập (leevawns) wrote :

nightly builds does not have this error

Changed in kicad:
importance: Undecided → Critical
milestone: none → 6.0.0-rc1
status: Incomplete → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.