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

Join throws many "GL errors" #6320

Closed
2 tasks done
xvcgreg opened this issue Apr 17, 2023 · 7 comments · Fixed by #6339
Closed
2 tasks done

Join throws many "GL errors" #6320

xvcgreg opened this issue Apr 17, 2023 · 7 comments · Fixed by #6339
Assignees
Labels
--bug Type: bug --regression Important: regression

Comments

@xvcgreg
Copy link

xvcgreg commented Apr 17, 2023

Discord username

No response

What type of issue is this?

Permanent – Ocurring repeatably

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

What issue are you facing?

Whenever I'm placing Join method I'm getting bunch of GL errors:

[26212:0417/215009.751:ERROR:gl_utils.cc(398)] [.WebGL-00003AFC06691B00] GL_INVALID_OPERATION: Error: 0x00000502, in ..\..\third_party\angle\src\libANGLE\renderer\d3d\VertexDataManager.cpp, reserveSpaceForAttrib:520. Internal error: 0x00000502: Vertex buffer is not big enough for the draw call.
[26212:0417/215009.766:ERROR:logger.cc(46)] Too many GL errors, not reporting any more for this context. use --disable-gl-error-limit to see all errors.

eventually (usually 3rd or 4th join) engine crashes i get this partial line:

[29508:0417/215657.798:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is

and no further working with Enso is possible.

Expected behaviour

Join working

How we can reproduce it?

read some large CSV file like one from BC10
and try to inner join it

Screenshots or screencasts

No response

Enso Version

2023.04.15

Browser or standalone distribution

Standalone distribution

Browser Version or standalone distribution

standalone

Operating System

Windows

Operating System Version

11pro 22H2

Hardware you are using

12th Gen Intel(R) Core(TM) i9-12900HK / RTX3060 Laptop

@xvcgreg
Copy link
Author

xvcgreg commented Apr 17, 2023

At this point it's also triggered by changing project name:

2304172209_shareX.mp4

@enso-bot
Copy link

enso-bot bot commented Apr 18, 2023

Keziah Wesley reports a new STANDUP for today (2023-04-17):

Progress: Debugging issue. Found a logic bug in related code, but it is apparently not the cause of the observed behavior. It should be finished by 2023-04-19.

Next Day: Next day I will be working on the #6320 task. Continue debugging.

@sylwiabr sylwiabr added -gui and removed triage labels Apr 18, 2023
@xvcgreg
Copy link
Author

xvcgreg commented Apr 18, 2023

@kazcw What caused this regression? Please update this information.

@xvcgreg
Copy link
Author

xvcgreg commented Apr 18, 2023

Log from todays build
log for 6320 regression build 2023.04.18.txt

@kazcw
Copy link
Contributor

kazcw commented Apr 18, 2023

It was caused by #6202. I tested it on Linux, possibly no one tested in on Windows.

@mergify mergify bot closed this as completed in #6339 Apr 18, 2023
@github-project-automation github-project-automation bot moved this from 🔧 Implementation to 🟢 Accepted in Issues Board Apr 18, 2023
mergify bot pushed a commit that referenced this issue Apr 18, 2023
@enso-bot
Copy link

enso-bot bot commented Apr 20, 2023

Keziah Wesley reports a new STANDUP for yesterday (2023-04-18):

Progress: Continuing to debug GL error. I have ruled out almost everything. It should be finished by 2023-04-19.

Next Day: Next day I will be working on the #6320 task. Continue debugging.

@enso-bot
Copy link

enso-bot bot commented Apr 20, 2023

Keziah Wesley reports a new STANDUP for today (2023-04-19):

Progress: Fixed the problem. Helped debug a backend crash that was only showing up on my machine. Picked another bug to look in to, but could not reproduce it. It should be finished by 2023-04-19.

Next Day: Next day I will be working on the #6320 task. Work on another bug, to be chosen tomorrow.

@farmaazon farmaazon moved this from 🟢 Accepted to 🗄️ Archived in Issues Board May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
--bug Type: bug --regression Important: regression
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants