Replies: 1 comment 2 replies
-
Converted to a discussion since as documented in the contribution guidelines we don’t promote to issues until we have an independent reproduction. Are you able to share the 500 bytes of the file that cause the crash? Or a debug build stack trace? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a
pg_dump --format=c
database dump file at 8.4 MB.If I run
head -n 10 db.dump
, I get the first lines (which happen to be text).Same for
-n 100
.With
-n 500
, I start getting to the binary part of the file. Most is printed out, but some command characters are left in the prompt:With
-n 800
it's a straight crash to desktop.With
-n 1000
the application becomes unresponsive (beach balling) and needs to be force quit.Running
cat
on the file is also crashes immediately.Beta Was this translation helpful? Give feedback.
All reactions