Bug 1370 - PulseView Crash at loading, when MCP2221 is connected
Summary: PulseView Crash at loading, when MCP2221 is connected
Status: RESOLVED DUPLICATE of bug 1031
Alias: None
Product: PulseView
Classification: Unclassified
Component: Other (show other bugs)
Version: 0.4.1
Hardware: x86 Windows
: Normal normal
Target Milestone: ---
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-23 11:55 CET by Christos
Modified: 2019-06-30 14:42 CEST (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christos 2019-03-23 11:55:30 CET 
running in Windwos 7 64 bit 

When PulseView start's AND a MCP2221 usb>serial converted is connected,
PulseView crashes during loading fx2lafw at 3% loading

tried both 32bit version of pulseview and 64bit, stable 0.4.1 and latest build (today)

when another usb converted is connected (ch340/FTDI) it does NOT crash

if i start pulseview with pulseview -D, option it does NOT crash at loading
however if i "select device" and choose anything from the list it does crash.

i tried changing driver with zadig to CDC, but crashes again

MCP2221 VID=04D8 PID=00DD
Comment 1 Uwe Hermann 2019-06-30 14:42:04 CEST 
Thanks for the bug report!

I've been able to reproduce this with an MCP2221 device I bought. After some digging, it turns out this is caused by various scpi-serial drivers, e.g. gwinstek-gds-800 and others, more specifically by libserialport's sp_list_ports().

Turns out the non-obvious root cause for this is a crash caused by the issue mentioned in bug #1031, which is now fixed.

New nightly Windows installers are now available and should no longer lead to crashes with MCP2221 and potentially other devices.

*** This bug has been marked as a duplicate of bug 1031 ***