You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some sort of JS Exception to be able to handle the error
What do you see instead?
Segmentation fault at address 0x8
???:?:?: 0x7ff6e2674cc6 in ??? (bun.exe)
???:?:?: 0x7ff6e2937fc4 in ??? (bun.exe)
???:?:?: 0x7ff6e293813e in ??? (bun.exe)
???:?:?: 0x7ff6e27c5645 in ??? (bun.exe)
???:?:?: 0x7ff6e261aa49 in ??? (bun.exe)
???:?:?: 0x7ff6e261ac28 in ??? (bun.exe)
???:?:?: 0x7ff6e4056f14 in ??? (bun.exe)
???:?:?: 0x7ff6e401f0fa in ??? (bun.exe)
???:?:?: 0x7ff6e4025e24 in ??? (bun.exe)
???:?:?: 0x7ff6e40921fd in ??? (bun.exe)
???:?:?: 0x7ff6e3fcc698 in ??? (bun.exe)
???:?:?: 0x7ff6e40a2ee6 in ??? (bun.exe)
???:?:?: 0x1ad02b0 in ??? (???)
???:?:?: 0x1f in ??? (???)
???:?:?: 0x1bde91ec2af in ??? (???)
Additional information
No response
The text was updated successfully, but these errors were encountered:
What version of Bun is running?
1.0.28
What platform is your computer?
MINGW64_NT-10.0-22621 3.3.5-341.x86_64 x86_64 unknown (WSL)
What steps can reproduce the bug?
an invalid PK
call the importKey function with the invalid key
What is the expected behavior?
Some sort of JS Exception to be able to handle the error
What do you see instead?
Segmentation fault at address 0x8
???:?:?: 0x7ff6e2674cc6 in ??? (bun.exe)
???:?:?: 0x7ff6e2937fc4 in ??? (bun.exe)
???:?:?: 0x7ff6e293813e in ??? (bun.exe)
???:?:?: 0x7ff6e27c5645 in ??? (bun.exe)
???:?:?: 0x7ff6e261aa49 in ??? (bun.exe)
???:?:?: 0x7ff6e261ac28 in ??? (bun.exe)
???:?:?: 0x7ff6e4056f14 in ??? (bun.exe)
???:?:?: 0x7ff6e401f0fa in ??? (bun.exe)
???:?:?: 0x7ff6e4025e24 in ??? (bun.exe)
???:?:?: 0x7ff6e40921fd in ??? (bun.exe)
???:?:?: 0x7ff6e3fcc698 in ??? (bun.exe)
???:?:?: 0x7ff6e40a2ee6 in ??? (bun.exe)
???:?:?: 0x1ad02b0 in ??? (???)
???:?:?: 0x1f in ??? (???)
???:?:?: 0x1bde91ec2af in ??? (???)
Additional information
No response
The text was updated successfully, but these errors were encountered: