<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Assets causing page crash error]]></title><description><![CDATA[<p>Hi I have been using js reports for a few months now and its been working perfectly.</p>
<p>I have a few schedules reports which are sent on the first of every month and this months reports werent sent. I then investigated the issue and just kept seeing the error <code>page crashed</code> which I know isnt very useful to anyone.</p>
<p>I started to strip my code bit by bit and then realised it was the asset images which were causing the page to crash. When all the images were removed the reports started working again.</p>
<p>I havent touched this code for months and it has been working fine every month leading up to this one. I was just wondering if anyone else has been experiencing this issue because it seems strange it has appeared without me touching the code.</p>
]]></description><link>https://forum.jsreport.net/topic/1855/assets-causing-page-crash-error</link><generator>RSS for Node</generator><lastBuildDate>Wed, 17 Jun 2026 06:28:40 GMT</lastBuildDate><atom:link href="https://forum.jsreport.net/topic/1855.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 02 Jan 2021 13:01:03 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Assets causing page crash error on Sat, 02 Jan 2021 13:01:46 GMT]]></title><description><![CDATA[<p>Hi I have been using js reports for a few months now and its been working perfectly.</p>
<p>I have a few schedules reports which are sent on the first of every month and this months reports werent sent. I then investigated the issue and just kept seeing the error <code>page crashed</code> which I know isnt very useful to anyone.</p>
<p>I started to strip my code bit by bit and then realised it was the asset images which were causing the page to crash. When all the images were removed the reports started working again.</p>
<p>I havent touched this code for months and it has been working fine every month leading up to this one. I was just wondering if anyone else has been experiencing this issue because it seems strange it has appeared without me touching the code.</p>
]]></description><link>https://forum.jsreport.net/post/8241</link><guid isPermaLink="true">https://forum.jsreport.net/post/8241</guid><dc:creator><![CDATA[Lukerayn3r]]></dc:creator><pubDate>Sat, 02 Jan 2021 13:01:46 GMT</pubDate></item><item><title><![CDATA[Reply to Assets causing page crash error on Invalid Date]]></title><description><![CDATA[<p>Hi, the chrome page crash can mean it used all of the memory.<br />
As you found, this can be caused by the images.<br />
Images are a bit tricky, if you put an image with a modified width/height attributes to HTML, the chrome still embeds the full-size images to the pdf and this is consuming a lot of memory. If this is your case, I recommend resizing your physical images upfront to the desired size. You can do this manually or programmatically.<br />
See an example here:<br />
<a href="https://jsreport.net/learn/templating-engines#asynchronous-helpers" rel="nofollow">https://jsreport.net/learn/templating-engines#asynchronous-helpers</a></p>
]]></description><link>https://forum.jsreport.net/post/8247</link><guid isPermaLink="true">https://forum.jsreport.net/post/8247</guid><dc:creator><![CDATA[jan_blaha]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>