Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing Serial Port on Windows Causes JRE Crash #71

Closed
retiutut opened this issue Feb 1, 2020 · 14 comments · Fixed by #75
Closed

Accessing Serial Port on Windows Causes JRE Crash #71

retiutut opened this issue Feb 1, 2020 · 14 comments · Fixed by #75
Assignees

Comments

@retiutut
Copy link

retiutut commented Feb 1, 2020

Description

OpenBCI/OpenBCI_GUI#674

Expected Behavior

Access Serial ports directly on Windows without the JRE crashing.

Current Behavior

Crashes and produces a log in the application directory. Happens on Standalone app and processing-java.

Steps to Reproduce

  1. Download OpenBCI GUI v4.2.0 pre-release.
  2. Open GUI, and hopefully you have some serial ports to populate the list (e.g. COM1, COM2, etc.)
  3. In the control panel, click: Live(from Cyton)-->Serial(from Dongle)-->Manual > -->Any Radio Configuration Button

Your Environment

  • Processing version: 4.0.0-alpha1
  • Operating System and OS version: Windows 10 Pro - up to date
  • Other information:

Possible Causes / Solutions

Probably crashing on the following line:

serial_output = new Serial(this, openBCI_portName, openBCI_baud); //open the com port

hs_err_pid11188.log
hs_err_pid2120.log

@retiutut retiutut changed the title Accessing Accessing Serial Port on Windows Causes JRE Crash Feb 1, 2020
@retiutut
Copy link
Author

retiutut commented Feb 2, 2020

Happens using the Processing-IDE and the example from the Processing docs also:

https://processing.org/reference/libraries/serial/Serial.html

@sampottinger
Copy link
Collaborator

Hey @retiutut thanks for posting this! I'll take a look. For folks following along at home, not reproducing on Mac but I'll give it a go on Windows in a minute.

@sampottinger sampottinger self-assigned this Feb 3, 2020
@retiutut
Copy link
Author

retiutut commented Feb 3, 2020

That's correct. Seem's to work just fine on Ubuntu Linux and OS X Catalina.

@sampottinger
Copy link
Collaborator

Was able to reproduce on Windows 10 (non JVM access violation!). We will dig in.

@sampottinger
Copy link
Collaborator

Looks like we need to update! https://github.com/java-native/jssc/releases/tag/v2.9.0 or https://github.com/akuhtz/spsw. I'll give it a shot. Just FYI... this fork seems like the active continuation of the now dead original.

@sampottinger
Copy link
Collaborator

See ... https://github.com/sampottinger/jssc. Looks like there's still some work to do here.

@benfry
Copy link
Owner

benfry commented Mar 7, 2020

Thanks for looking into it, @sampottinger

@sampottinger
Copy link
Collaborator

Of course! A quick update... I think I sorted it on windows but have mac build issues. Hoping to have more soon.

@sampottinger
Copy link
Collaborator

Blocked on #73

sampottinger added a commit that referenced this issue Mar 8, 2020
Started migration of JSSC in response to #71, introducing mac os in this commit.
@sampottinger
Copy link
Collaborator

Yay! See the JSSC migration branch. I've tested for Linux 64 bit, Windows 64 bit, and Mac.

Screen Shot 2020-03-08 at 11 59 17 AM

@benfry
Copy link
Owner

benfry commented Apr 27, 2020

Merged the fix from Sam for alpha 2.

@retiutut
Copy link
Author

Awesome! Thanks!

@retiutut
Copy link
Author

retiutut commented May 2, 2020

@benfry When will alpha 2 release be published?

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants