Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Frequently encounter Segmentation fault (exit code 139) when using rsbuild dev server, how to reproduce#11266

Unanswered
yf-yang asked this question inQ&A
Discussion options

In my code base I frequently encounter seg fault, almost every 4~5 times rebuild will trigger one. However, I cannot easily reproduce that with a minimal repository. Is there any way I can check some logs and narrow down the root cause?

I've triedRSPACK_PROFILE=trace RSPACK_PROFILE=ALL RSPACK_TRACE_LAYER=logger RSPACK_TRACE_OUTPUT=./log.txt rsbuild dev, but didn't find any useful clues

You must be logged in to vote

Replies: 1 comment 4 replies

Comment options

Is it possible to file an issue and grant access of my private repo to a rspack maintainer?

You must be logged in to vote
4 replies
@chenjiahan
Comment options

If possible, could you give me access to the private repository?

@yf-yang
Comment options

Sure, I'll DM you in discord to discuss. Thank you for your help. I'm really appreciating it

@chenjiahan
Comment options

Thanks for your invitation. I can't seem to reproduce the issue by triggering rebuilds. Can you provide other ways to reproduce it?

image
@yf-yang
Comment options

Did you open localhost:3000 in the browser? If not opening the page, it runs perfectly fine.
Also, color.tsx is only used in storybook.
If still difficult to reproduce, try to start in a memory constrained (maybe also constrain available cpu kernel numbers?) container.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
2 participants
@yf-yang@chenjiahan
[8]ページ先頭
©2009-2025 Movatter.jp