-
Notifications
You must be signed in to change notification settings - Fork 180
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
Segmentation fault with ruby 2.7.8 and pg 1.5.3 #536
Comments
Can you get a C level backtrace? It usually looks like here. |
Here it is for ruby 3.0.6, can't have the 2.7.8 one:
|
I can't provide much information for this, but we're seeing a crash with ruby 2.7.8 on windows with the PG gem, but the only thing windows is reporting about the error is error code -1073740940, which I think is a heap stack corruption. |
@larskanis Found the ruby 2.7.8 C backtrace.
|
Both ruby versions crash on The only other reason for a crash, I could imagine, is that the It could help to reproduce the segfault in a gdb session. On modern Linux distributions like Ubuntu-23.04, gdb asks for download of debug symbols of system libraries, so that we could see, within which function and source line libpq crashes. Beside this I don't have a good idea for now. So far it's the only bug report of this kind. |
Same issue here. |
Same issue:
|
similar issue with ruby
Update: |
FYI, you can also use Edit: while this helped, it didn't fix it in all cases |
Hi, We're facing a Segmentation fault with ruby 2.7.4 and pg 1.4.6 in a rails application (v6.1.7) in the mx-linux /home/brijesh/.rvm/gems/ruby-2.7.4@referalgps/gems/pg-1.4.6/lib/pg/connection.rb:627: [BUG] Segmentation fault at 0x0000000000000000 |
Hi, We're facing a Segmentation fault with ruby 2.7.8 and pg 1.5.3 in a rails application (v6.1.7). This is sometimes happening in CI. It is sometimes reproducible locally but I haven't found the right conditions to always reproduce the issue.
Stack trace
Actual failing code
Is there anything I can try to fix it ?
Maybe the answer is to just upgrade ruby version.
[EDIT]
Also seeing the issue with ruby 3.0.6
The stack trace has more details with this ruby version.
The text was updated successfully, but these errors were encountered: