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

emscripten_stack_get_current not exported (recovered by wazero) #2317

Closed
88250 opened this issue Sep 20, 2024 · 4 comments
Closed

emscripten_stack_get_current not exported (recovered by wazero) #2317

88250 opened this issue Sep 20, 2024 · 4 comments

Comments

@88250
Copy link

88250 commented Sep 20, 2024

Describe the bug

Can't parse the file.

sample.pdf

[emscripten_stack_get_current not exported (recovered by wazero)
wasm stack trace:
	env.invoke_iii(i32,i32,i32) i32
	.$1954(i32,i32,i32,i32,i32) i32
	.$1568(i32,i32,i32,i32,i32) i32
	.$1508(i32,i32,i32,i32,i32,i32,i32) i32
	.$2306(i32,i32,i32,i32) i32
	.$2350(i32,i32,i32,i64) i32
	.$2433(i32,i32)
	.$2404(i32) i32
	.$2411(i32) i32
	.$2436(i32,i32,i32) i32
	.$3919(i32,i32) i32
	.$3819(i32,i32) i32
	.$3818(i32)
	.$3875(i32,i32)
	.$3575(i32)
	.$5025(i32,i32) i32]

To Reproduce

https://github.com/siyuan-note/siyuan/blob/3eec016723f52f3a679fb99854ae33e8fe20e42a/kernel/model/asset_content.go#L883

Expected behavior

Parse sucesses.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the relevant information):

  • Go version: go1.23.1
  • wazero Version: 1.8.0
  • Host architecture: amd64
  • Runtime mode:

Additional context

@mathetake
Copy link
Member

Use the latest emscripten #2290

@mathetake mathetake removed the bug Something isn't working label Sep 21, 2024
@88250
Copy link
Author

88250 commented Sep 21, 2024

Hello, can you give me more detailed instructions? I have never manually installed emscripten.

@ncruces
Copy link
Collaborator

ncruces commented Sep 21, 2024

You seem to be using github.com/klippa-app/go-pdfium. They use wazero 1.7.3, you upgraded to v1.8.0. don't do that. Wait for them to upgrade.

@88250
Copy link
Author

88250 commented Sep 21, 2024

It is indeed a version mismatch problem, thank you very much for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants