github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Bus error (webpack) when building Gitea #12438

New Issue
Closed
opened 2025-11-02 10:09:49 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-02 10:09:49 -06:00
Owner
Copy Link

Originally created by @bagasme on GitHub (Feb 5, 2024).

Description

Hi,

I'm trying to build Gitea on commit 4bb1fcd2e7, following build instructions. Node.js used is v18.19.0.

As I run make, the build stopped on webpack where webpack core dumped due to bus error (AFAIK, it because my Intel core i3 haswell processor can't attempt memory requests from node).

After examining the dump info (via coredumpctl info), it turns out that lightningcss module causes the webpack error.

This build issue is also reproduced on node v20.11.0.

Gitea Version

commit 4bb1fcd2e7

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/bagasme/d58a38beac308a20aa3b40dda2285021

Screenshots

n/a

Git Version

n/a

Operating System

Arch Linux

How are you running Gitea?

Building from source (node v18.19.0, go 1.21.6).

npx webpack info output:


  System:
    OS: Linux 6.8 Arch Linux
    CPU: (4) x64 Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz
    Memory: 1.31 GB / 3.73 GB
  Binaries:
    Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node
    npm: 10.2.3 - ~/.nvm/versions/node/v18.19.0/bin/npm
  Packages:
    add-asset-webpack-plugin: 2.0.1 => 2.0.1 
    css-loader: 6.10.0 => 6.10.0 
    esbuild-loader: 4.0.3 => 4.0.3 
    license-checker-webpack-plugin: 0.2.1 => 0.2.1 
    lightningcss-loader: 2.1.0 => 2.1.0 
    monaco-editor-webpack-plugin: 7.1.0 => 7.1.0 
    vue-loader: 17.4.2 => 17.4.2 
    webpack: 5.90.1 => 5.90.1 
    webpack-cli: 5.1.4 => 5.1.4

Database

None

Originally created by @bagasme on GitHub (Feb 5, 2024). ### Description Hi, I'm trying to build Gitea on commit 4bb1fcd2e727c3514658d720abed145ca751049f, following [build instructions](https://docs.gitea.com/next/installation/install-from-source). Node.js used is v18.19.0. As I run `make`, the build stopped on webpack where webpack core dumped due to bus error (AFAIK, it because my Intel core i3 haswell processor can't attempt memory requests from node). After examining the dump info (via `coredumpctl info`), it turns out that lightningcss module causes the webpack error. This build issue is also reproduced on node v20.11.0. ### Gitea Version commit 4bb1fcd2e727c3514658d720abed145ca751049f ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist https://gist.github.com/bagasme/d58a38beac308a20aa3b40dda2285021 ### Screenshots n/a ### Git Version n/a ### Operating System Arch Linux ### How are you running Gitea? Building from source (node v18.19.0, go 1.21.6). `npx webpack info` output: ``` System: OS: Linux 6.8 Arch Linux CPU: (4) x64 Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz Memory: 1.31 GB / 3.73 GB Binaries: Node: 18.19.0 - ~/.nvm/versions/node/v18.19.0/bin/node npm: 10.2.3 - ~/.nvm/versions/node/v18.19.0/bin/npm Packages: add-asset-webpack-plugin: 2.0.1 => 2.0.1 css-loader: 6.10.0 => 6.10.0 esbuild-loader: 4.0.3 => 4.0.3 license-checker-webpack-plugin: 0.2.1 => 0.2.1 lightningcss-loader: 2.1.0 => 2.1.0 monaco-editor-webpack-plugin: 7.1.0 => 7.1.0 vue-loader: 17.4.2 => 17.4.2 webpack: 5.90.1 => 5.90.1 webpack-cli: 5.1.4 => 5.1.4 ``` ### Database None
GiteaMirror added the type/bugtype/upstream labels 2025-11-02 10:09:49 -06:00
GiteaMirror commented 2025-11-02 10:09:50 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 5, 2024):

I guess it is a upstream problem (as you mentioned: lightningcss), so Gitea could do nothing IMO?

Could you report the problem to upstream?

@wxiaoguang commented on GitHub (Feb 5, 2024): I guess it is a upstream problem (as you mentioned: lightningcss), so Gitea could do nothing IMO? Could you report the problem to upstream?
GiteaMirror commented 2025-11-02 10:09:50 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 5, 2024):

The intention is that it should fall back to esbuild in case lightningcss crashes, but it appears we only catch startup crashes, not runtime crashes:

6992ef98fc/webpack.config.js (L58-L62)

We could also just remove lightningcss if this turns out to be not fixable from our end. It will give slightly larger CSS files, but esbuild is arguably much more battle-tested.

@silverwind commented on GitHub (Feb 5, 2024): The intention is that it should fall back to esbuild in case lightningcss crashes, but it appears we only catch startup crashes, not runtime crashes: https://github.com/go-gitea/gitea/blob/6992ef98fc227a60cf06e0a06b9ae2492b3d61be/webpack.config.js#L58-L62 We could also just remove lightningcss if this turns out to be not fixable from our end. It will give slightly larger CSS files, but esbuild is arguably much more battle-tested.
GiteaMirror commented 2025-11-02 10:09:50 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 5, 2024):

@bagasme Can you try if this changes anything?

NODE_OPTIONS="--max-old-space-size=4096" make webpack

This is more memory than your system has but I assume you have a swap file.

@silverwind commented on GitHub (Feb 5, 2024): @bagasme Can you try if this changes anything? ``` NODE_OPTIONS="--max-old-space-size=4096" make webpack ``` This is more memory than your system has but I assume you have a swap file.
GiteaMirror commented 2025-11-02 10:09:50 -06:00
Author
Owner
Copy Link

@bagasme commented on GitHub (Feb 5, 2024):

@bagasme Can you try if this changes anything?

NODE_OPTIONS="--max-old-space-size=4096" make webpack

This is more memory than your system has but I assume you have a swap file.

Nope. I can still reproduce the webpack bus error.

@bagasme commented on GitHub (Feb 5, 2024): > @bagasme Can you try if this changes anything? > > ``` > NODE_OPTIONS="--max-old-space-size=4096" make webpack > ``` > > This is more memory than your system has but I assume you have a swap file. Nope. I can still reproduce the webpack bus error.
GiteaMirror commented 2025-11-02 10:09:50 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 5, 2024):

Hmm, so I guess your system may have too little memory for lightningcss to run. Do you have a swap file, and if not, create one? I would recomment at least 8GB size.

@silverwind commented on GitHub (Feb 5, 2024): Hmm, so I guess your system may have too little memory for lightningcss to run. Do you have a swap file, and if not, create one? I would recomment at least 8GB size.
GiteaMirror commented 2025-11-02 10:09:50 -06:00
Author
Owner
Copy Link

@bagasme commented on GitHub (Feb 5, 2024):

I guess it is a upstream problem (as you mentioned: lightningcss), so Gitea could do nothing IMO?

Could you report the problem to upstream?

Done at parcel-bundler/lightningcss#671.

@bagasme commented on GitHub (Feb 5, 2024): > I guess it is a upstream problem (as you mentioned: lightningcss), so Gitea could do nothing IMO? > > Could you report the problem to upstream? Done at parcel-bundler/lightningcss#671.
GiteaMirror commented 2025-11-02 10:09:51 -06:00
Author
Owner
Copy Link

@bagasme commented on GitHub (Feb 5, 2024):

Hmm, so I guess your system may have too little memory for lightningcss to run. Do you have a swap file, and if not, create one? I would recomment at least 8GB size.

Yes, I have 4GB RAM + 4.41GiB swap.

@bagasme commented on GitHub (Feb 5, 2024): > Hmm, so I guess your system may have too little memory for lightningcss to run. Do you have a swap file, and if not, create one? I would recomment at least 8GB size. Yes, I have 4GB RAM + 4.41GiB swap.
GiteaMirror commented 2025-11-02 10:09:51 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 5, 2024):

Thanks, so let's see what comes out of the issue. I'm still leaning towards removing lightningcss, it just seems not stable enough.

@silverwind commented on GitHub (Feb 5, 2024): Thanks, so let's see what comes out of the issue. I'm still leaning towards removing lightningcss, it just seems not stable enough.
GiteaMirror commented 2025-11-02 10:09:51 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 5, 2024):

@bagasme can you try this patch on the affected machine?

diff --git a/webpack.config.js b/webpack.config.js
index c4b140a12b..16afa0ff9c 100644
--- a/webpack.config.js
+++ b/webpack.config.js
@@ -54,14 +54,8 @@ const filterCssImport = (url, ...args) => {

   return true;
 };

-// in case lightningcss fails to load, fall back to esbuild for css minify
-let LightningCssMinifyPlugin;
-try {
-  ({LightningCssMinifyPlugin} = await import('lightningcss-loader'));
-} catch {}
-
 /** @type {import("webpack").Configuration} */
 export default {
   mode: isProduction ? 'production' : 'development',
   entry: {
@@ -105,14 +99,11 @@ export default {
     minimizer: [
       new EsbuildPlugin({
         target: 'es2020',
         minify: true,
-        css: !LightningCssMinifyPlugin,
+        css: true,
         legalComments: 'none',
       }),
-      LightningCssMinifyPlugin && new LightningCssMinifyPlugin({
-        sourceMap: sourceMaps === 'true',
-      }),
     ],
     splitChunks: {
       chunks: 'async',
       name: (_, chunks) => chunks.map((item) => item.name).join('-'),
@silverwind commented on GitHub (Feb 5, 2024): @bagasme can you try this patch on the affected machine? ```patch diff --git a/webpack.config.js b/webpack.config.js index c4b140a12b..16afa0ff9c 100644 --- a/webpack.config.js +++ b/webpack.config.js @@ -54,14 +54,8 @@ const filterCssImport = (url, ...args) => { return true; }; -// in case lightningcss fails to load, fall back to esbuild for css minify -let LightningCssMinifyPlugin; -try { - ({LightningCssMinifyPlugin} = await import('lightningcss-loader')); -} catch {} - /** @type {import("webpack").Configuration} */ export default { mode: isProduction ? 'production' : 'development', entry: { @@ -105,14 +99,11 @@ export default { minimizer: [ new EsbuildPlugin({ target: 'es2020', minify: true, - css: !LightningCssMinifyPlugin, + css: true, legalComments: 'none', }), - LightningCssMinifyPlugin && new LightningCssMinifyPlugin({ - sourceMap: sourceMaps === 'true', - }), ], splitChunks: { chunks: 'async', name: (_, chunks) => chunks.map((item) => item.name).join('-'),
GiteaMirror commented 2025-11-02 10:09:51 -06:00
Author
Owner
Copy Link

@bagasme commented on GitHub (Feb 6, 2024):

@bagasme can you try this patch on the affected machine?

diff --git a/webpack.config.js b/webpack.config.js
index c4b140a12b..16afa0ff9c 100644
--- a/webpack.config.js
+++ b/webpack.config.js
@@ -54,14 +54,8 @@ const filterCssImport = (url, ...args) => {

   return true;
 };

-// in case lightningcss fails to load, fall back to esbuild for css minify
-let LightningCssMinifyPlugin;
-try {
-  ({LightningCssMinifyPlugin} = await import('lightningcss-loader'));
-} catch {}
-
 /** @type {import("webpack").Configuration} */
 export default {
   mode: isProduction ? 'production' : 'development',
   entry: {
@@ -105,14 +99,11 @@ export default {
     minimizer: [
       new EsbuildPlugin({
         target: 'es2020',
         minify: true,
-        css: !LightningCssMinifyPlugin,
+        css: true,
         legalComments: 'none',
       }),
-      LightningCssMinifyPlugin && new LightningCssMinifyPlugin({
-        sourceMap: sourceMaps === 'true',
-      }),
     ],
     splitChunks: {
       chunks: 'async',
       name: (_, chunks) => chunks.map((item) => item.name).join('-'),

Webpack build passed (no errors).

@bagasme commented on GitHub (Feb 6, 2024): > @bagasme can you try this patch on the affected machine? > > ```diff > diff --git a/webpack.config.js b/webpack.config.js > index c4b140a12b..16afa0ff9c 100644 > --- a/webpack.config.js > +++ b/webpack.config.js > @@ -54,14 +54,8 @@ const filterCssImport = (url, ...args) => { > > return true; > }; > > -// in case lightningcss fails to load, fall back to esbuild for css minify > -let LightningCssMinifyPlugin; > -try { > - ({LightningCssMinifyPlugin} = await import('lightningcss-loader')); > -} catch {} > - > /** @type {import("webpack").Configuration} */ > export default { > mode: isProduction ? 'production' : 'development', > entry: { > @@ -105,14 +99,11 @@ export default { > minimizer: [ > new EsbuildPlugin({ > target: 'es2020', > minify: true, > - css: !LightningCssMinifyPlugin, > + css: true, > legalComments: 'none', > }), > - LightningCssMinifyPlugin && new LightningCssMinifyPlugin({ > - sourceMap: sourceMaps === 'true', > - }), > ], > splitChunks: { > chunks: 'async', > name: (_, chunks) => chunks.map((item) => item.name).join('-'), > ``` Webpack build passed (no errors).
GiteaMirror commented 2025-11-02 10:09:51 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 6, 2024):

https://github.com/go-gitea/gitea/pull/29070 will fix it by removing lightningcss. We can reconsider once it becomes more stable.

@silverwind commented on GitHub (Feb 6, 2024): https://github.com/go-gitea/gitea/pull/29070 will fix it by removing lightningcss. We can reconsider once it becomes more stable.
GiteaMirror commented 2025-11-02 10:09:52 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 28, 2024):

Automatically locked because of our CONTRIBUTING guidelines

@github-actions[bot] commented on GitHub (Feb 28, 2024): Automatically locked because of our [CONTRIBUTING guidelines](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#issue-locking)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug type/upstream
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12438
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?