[Bug report] 0.47.7 crashes when deploying a newly created site or after changing server settings #2631
Replies: 12 comments 1 reply
|
Hi, I am unable to reproduce this issue - I have tried to change server settings on existing websites and also create a new website -> change header text -> save and preview -> set server settings to manual deploy -> then deploy. Also preview works for both test websites. Tested on mac os and windows version. Could you try to reproduce the issue and check error logs under log viewer? Especially:
Maybe it will reveal reason of your issues? |
|
Hi, thank you for relying.
After reverting to 0.47.6 and then reinstalling 0.47.7 syncing worked, but
clicking on "Preview your changes" brings this message:
core.rendering.renderingProcessCrashed
core.rendering.renderingProcessCrashedMsg
[image: image.png]
*rendering-deployment-process.log*
CONFIG: 52.83ms
FEATURED TAG IMAGES - QUERY: 0.785ms
FEATURED TAG IMAGES - STORE: 0.005ms
TAGS POST COUNT - QUERY: 0.212ms
TAGS POST COUNT - STORE: 0.009ms
MAINTAGS - QUERY: 0.222ms
TAGS - QUERY: 0.14ms
TAGS - STORE: 0.01ms
FEATURED AUTHOR IMAGES - QUERY: 0.137ms
FEATURED AUTHOR IMAGES - STORE: 0.006ms
AUTHORS POST COUNT - QUERY: 0.145ms
AUTHORS POST COUNT - STORE: 0.007ms
AUTHORS - QUERY: 0.129ms
AUTHORS - STORE: 1.586ms
FEATURED POST IMAGES - QUERY: 0.143ms
FEATURED POST IMAGES - STORE: 0.002ms
FEATURED PAGE IMAGES - QUERY: 0.179ms
FEATURED PAGE IMAGES - STORE: 0.304ms
POST TAGS - QUERY: 0.135ms
POST TAGS - STORE: 0.003ms
POSTS - QUERY: 0.18ms
POSTS - STORE: 0.009ms
PAGES - QUERY: 0.181ms
PAGES - STORE: 4.267ms
CONTENT DATA: 22.746ms
COMMON DATA: 2.445ms
PARTIALS GENERATION: 260.167ms
CSS stats: 0.20354275741710293 (45637/57300)
CSS: 215.316ms
HOMEPAGE: 101.783ms
POSTS: 10.912ms
PAGES: 31.566ms
TAGS: 12.256ms
TAGS-LIST: 30.346ms
AUTHORS: 28.446ms
404: 29.618ms
FEEDS: 16.941ms
[OK] Deleted empty directory:
D:\Onedrive\sites\homeoainet\output\media\authors
[OK] Deleted empty directory:
D:\Onedrive\sites\homeoainet\output\media\files
[OK] Deleted empty directory:
D:\Onedrive\sites\homeoainet\output\media\posts
[OK] Deleted empty directory:
D:\Onedrive\sites\homeoainet\output\media\tags
[OK] Deleted empty directory:
D:\Onedrive\sites\homeoainet\output\media\website
[OK] Deleted empty directory: D:\Onedrive\sites\homeoainet\output\media
FILES: 146.858ms
SITEMAP: 26.389ms
RENDERING: 1.043s
*rendering-deployment-errors.log*
*rendering-process.logrendering-errors.log*
The log file is empty...
Going back to 0.47.6 "Preview your changes" and everything else works
Thanks
Adrian
…On Thu, Jul 9, 2026 at 10:30 AM Tomasz Dziuda ***@***.***> wrote:
Hi,
I am unable to reproduce this issue - I have tried to change server
settings on existing websites and also create a new website -> change
header text -> save and preview -> set server settings to manual deploy ->
then deploy. Also preview works for both test websites.
Tested on mac os and windows version.
Could you try to reproduce the issue and check error logs under log viewer?
Especially:
- rendering-deployment-process.log
- rendering-deployment-errors.log
- rendering-process.log
- rendering-errors.log
Maybe it will reveal reason of your issues?
—
Reply to this email directly, view it on GitHub
<#2631?email_source=notifications&email_token=CH47AW4ARNSEKL2M7MPFGR35D5C2NA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZVHAYTQMJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17581819>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CH47AW3AVIMRB4MXC5BVKPL5D5C2NAVCNFSNUABIKJSXA33TNF2G64TZHMYTGNZXGMZTENRWHNCGS43DOVZXG2LPNY5TCMBTHE3DQOBRUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CH47AW7AHMI2D3DZFLVUQTL5D5C2NA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZVHAYTQMJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/CH47AW6M4ONDG6ZPECHFY4L5D5C2NA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZVHAYTQMJZUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi, @Adrian-Alecu i have the same problem with this version. I'm discovering Publii, and i'm fighting with it over 2 days. Maybe, to reproduce it, simple intall v0.47.7, create a site. Create a wab page and paste a valid HTML code. You should see this rendering error. Detete the page or anything do nothing. However, delete the "preview" directory in sites give a temporary fix. I have also some js error to write file. For example, i can't delete "simple" theme or others. I'm running on a fresh win11. This version has too much problems. Thanks |
|
@Adrian-Alecu @corso-66 - I have improved output of errors in this version: https://dziudek.pl/temp-file/Publii-0.47.8-prerelease.exe - could you check if the crash messages are now more readable and contains additional details? |
|
Hi Tomasz,
thank you for coming back.
Interestingly, no problem with this 0.47.8 prerelease, eveything works fine.
But reverting to 0.47.7 again:
core.rendering.renderingProcessCrashed
core.rendering.renderingProcessCrashedMsg
Adrian
…On Wed, Jul 22, 2026 at 10:57 AM Tomasz Dziuda ***@***.***> wrote:
@Adrian-Alecu <https://github.com/Adrian-Alecu> @corso-66
<https://github.com/corso-66> - I have improved output of errors in this
version: https://dziudek.pl/temp-file/Publii-0.47.8-prerelease.exe -
could you check if the crash messages are now more readable and contains
additional details?
—
Reply to this email directly, view it on GitHub
<#2631?email_source=notifications&email_token=CH47AW76XRYEHQ5IJMNBJE35GBXV7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGMYDGNRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17730363>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CH47AWZ2TVQFYNU545EOMSD5GBXV7AVCNFSNUABIKJSXA33TNF2G64TZHMYTGNZXGMZTENRWHNCGS43DOVZXG2LPNY5TCMBTHE3DQOBRUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CH47AW24XKJOCAN7WP3JBS35GBXV7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGMYDGNRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/CH47AW2WVDYEQOHTIVP2GST5GBXV7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGMYDGNRTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Adrian-Alecu - maybe it was related to the electron version? 0.47.8 used 41.9.1 while 0.47.8-prerelease uses 41.10.2 Anyway it's good to hear that your problem seems to be solved. We will wait for more feedback in few other threads and we will ofically release v.0.47.8 then :) |
|
Right, it could be an Electron bug.
Thanks!
Adrian
mie., 22 iul. 2026, 17:57 Tomasz Dziuda ***@***.***> a scris:
… @Adrian-Alecu <https://github.com/Adrian-Alecu> - maybe it was related to
the electron version? 0.47.8 used 41.9.1 while 0.47.8-prerelease uses
41.10.2
Anyway it's good to hear that your problem seems to be solved. We will
wait for more feedback in few other threads and we will ofically release
v.0.47.8 then :)
—
Reply to this email directly, view it on GitHub
<#2631?email_source=notifications&email_token=CH47AW7POW3AX3VRFM3R64L5GDI65A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGM3DMNZWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17736676>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CH47AW43LW6IMFRTXCW24DL5GDI65AVCNFSNUABIKJSXA33TNF2G64TZHMYTGNZXGMZTENRWHNCGS43DOVZXG2LPNY5TCMBTHE3DQOBRUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CH47AW4CXLUDSUR5PBMLIJ35GDI65A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGM3DMNZWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/CH47AW5MNN45WP5VO5HK7L35GDI65A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGM3DMNZWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Adrian-Alecu - Publii v.0.47.8 officially released with a few additional improvements :) |
|
Now trying the same brought again errors previewing a new website, either
with 0.47.8 and also when reverting to 0.47.8 prerelease. At the same
time, no problem with 0.47.6.
It looks like the path is not forming correctly, or file permissions are
not managed properly.
Because after reverting to 0.47.6 and previewing the new website, preview
folders created, then reinstalling 0.47.8 the preview works without errors
…__
Rendering process failed
EPERM, Permission denied: \\?\D:\Onedrive\sites\homeoainet\preview\authors
'\\?\D:\Onedrive\sites\homeoainet\preview\authors'
Error: EPERM, Permission denied:
\\?\D:\Onedrive\sites\homeoainet\preview\authors
'\\?\D:\Onedrive\sites\homeoainet\preview\authors'
at Object.rmSync (node:fs:1222:18)
at UtilsHelper.removePathRecursively
(C:\Users\adria\AppData\Local\Programs\Publii\resources\app.asar\back-end\helpers\utils.js:93:12)
at Renderer.emptyOutputDir
(C:\Users\adria\AppData\Local\Programs\Publii\resources\app.asar\back-end\modules\render-html\renderer.js:446:29)
at Renderer.render
(C:\Users\adria\AppData\Local\Programs\Publii\resources\app.asar\back-end\modules\render-html\renderer.js:117:20)
at process.
(C:\Users\adria\AppData\Local\Programs\Publii\resources\app.asar\back-end\workers\renderer\preview.js:17:37)
at process.emit (node:events:509:28)
at emit (node:internal/child_process:972:14)
at process.processTicksAndRejections
(node:internal/process/task_queues:91:21)
Adrian
On Thu, Jul 23, 2026 at 11:49 AM Tomasz Dziuda ***@***.***> wrote:
@Adrian-Alecu <https://github.com/Adrian-Alecu> - Publii v.0.47.8
officially released with a few additional improvements :)
—
Reply to this email directly, view it on GitHub
<#2631?email_source=notifications&email_token=CH47AW274TEM67VBQISBCIL5GHGR5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGQ3TCMRUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17747124>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CH47AWYSI6ZC7YRQAV4JZGD5GHGR5AVCNFSNUABIKJSXA33TNF2G64TZHMYTGNZXGMZTENRWHNCGS43DOVZXG2LPNY5TCMBTHE3DQOBRUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CH47AW62H3U5LRVTT6NCKGL5GHGR5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGQ3TCMRUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/CH47AW4526VPPWXUR4XZBKD5GHGR5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGQ3TCMRUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Adrian-Alecu - I have found a potential reason of this issue - newer version of Electron with newer Node.js probably causes this issue. They have changed a method of removing files. I have prepared a windows build which does file removal like in the older Node.js (with changing chmod when file returns EPERM). Could you check if this build works for you: https://dziudek.pl/temp-file/Publii-0.47.8-build-17480.exe ? |
|
Yep, this one seems to work
Adrian
…On Thu, Jul 23, 2026 at 7:39 PM Tomasz Dziuda ***@***.***> wrote:
@Adrian-Alecu <https://github.com/Adrian-Alecu> - I have found a
potential reason of this issue - newer version of Electron with newer
Node.js probably causes this issue. They have changed a method of removing
files. I have prepared a windows build which does file removal like in the
older Node.js (with changing chmod when file returns EPERM).
Could you check if this build works for you:
https://dziudek.pl/temp-file/Publii-0.47.8-build-17480.exe ?
—
Reply to this email directly, view it on GitHub
<#2631?email_source=notifications&email_token=CH47AW3NZXG2BZTXAD6EXVL5GI5VNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGU2DEMJVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17754215>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CH47AW5DWQU2HPHEJ3XBWJL5GI5VNAVCNFSNUABIKJSXA33TNF2G64TZHMYTGNZXGMZTENRWHNCGS43DOVZXG2LPNY5TCMBTHE3DQOBRUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CH47AW5BHTBZH7KVWVYE2FD5GI5VNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGU2DEMJVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/CH47AW32AKMM4TWF33U7EZT5GI5VNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZXGU2DEMJVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@dziudek hi ! 0.47.9 seem's running properly. Thank you Syl |
Uh oh!
There was an error while loading. Please reload this page.
Operating system
Windows 11
Publii version
0.47.7
Issue type
Application
Bug description
After upgrading to 0.47.7, updating existing websites works normally.
However, when I:
create a brand-new site, or
change the server configuration of an existing site,
the rendering process crashes when previewing or syncing.
The error dialog only shows:
Rendering process crashed
[object Object]
Workaround
Downgrading to Publii 0.47.6 fixes the issue immediately using the same project, same server and same settings.
This strongly suggests a regression introduced in 0.47.7.
Additional information
Existing sites continue to deploy successfully in 0.47.7.
The issue only appears when creating a new site or changing the server configuration.
Reverting to 0.47.6 resolves the problem completely.
Steps to reproduce
Duplicate a website and sync it to the server
Create a new wesite with a page, main menu and edit the hero section
Relevant log output
No response
All reactions