| Summary: | PulseView hangs randomly if left running (but not acquiring) when a new acquisition is started | ||
|---|---|---|---|
| Product: | PulseView | Reporter: | Joe Butler <ffffh> |
| Component: | Other | Assignee: | Nobody <nobody> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 0.4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Windows | ||
| Attachments: |
Attached Visual Studio Debugger after starting PulseView earlier
Process Explorer showing the same hang instance. |
||
Created attachment 745 [details]
Process Explorer showing the same hang instance.
This seems to happen after the pins of a FX2 device are reconnected to different points on a DUT. It is probably related to the FX2 temporarily loosing its USB connection for some reason (related to whether DUT is powered or not at the time of the re-wiring). |
Created attachment 744 [details] Attached Visual Studio Debugger after starting PulseView earlier PulseView can go for days or hours without crashing (when just left running, but not acquiring). But then when pressing the space bar or clicking Run to perform an acquisition, it will hang sometimes. I don't know if this is fact, but it seems more likely to hang if the sampling rate has been changed from what is first chosen before doing the first acquisition - but that may be superstition. I attached Visual Studio to PulseView after starting it and just left it running in the background while doing ad hoc acquisitions, and when PulseView crashed, I got this screenshot of Visual Studio - I don't know if it will help to determine where the crash/hang occurs.