- September 11, 2008 8:43 AM
-
An error: ERROR encountered loading https://myapp.company.net/reports/createReport.cfm: Failure in browser during Loading phase : Insufficient memory occured during the rendering process of this document.
I was having problems running a report in one of my ColdFusion 8 applications that generated a PDF, and in debugging the issue, I found an error message above. I've not seen it before, and I even tried using the interwebs to find the source, but to no avail.
The URLs have been changed for those that are wondering.
Detail |
[empty string] |
Message |
An error: ERROR encountered loading https://myapp.company.net/reports/createReport.cfm: Failure in browser during Loading phase : Insufficient memory occured during the rendering process of this document. |
StackTrace |
coldfusion.document.DocumentRenderException: An error: ERROR encountered loading https://myapp.company.net/reports/createReport.cfm: Failure in browser during Loading phase : Insufficient memory occured during the rendering process of this document. at coldfusion.tagext.lang.DocumentTag.doAfterBody(DocumentTag.java:1344) at cfschoolStudentLogin2ecfm337290575.runPage(D:\Websites\myapp.company.net\reports\createReport.cfm:79) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:196) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:370) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:273) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:86) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.RequestThrottleFilter.invoke(RequestThrottleFilter.java:126) at coldfusion.CfmServlet.service(CfmServlet.java:175) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at jrun.servlet.FilterChain.doFilter(FilterChain.java:86) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at jrun.servlet.FilterChain.doFilter(FilterChain.java:94) at jrun.servlet.FilterChain.service(FilterChain.java:101) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543) at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) |
TagContext |
Array
1 |
Struct
COLUMN |
0 |
ID |
CFDOCUMENT |
LINE |
79 |
RAW_TRACE |
at cfcreatereport2ecfm337290575.runPage(D:\Websites\myapp.company.net\reports\createReport.cfm:79) |
TEMPLATE |
D:\Websites\myapp.company.net\reports\createReport.cfm |
TYPE |
CFML |
|
|
Type |
Application |
errMsg |
ERROR encountered loading https://myapp.company.net/reports/createReport.cfm: Failure in browser during Loading phase : Insufficient memory |
Its a big file, so I'm not surprised something is off, but this message actually cites the browser as the source of the issue. I was hitting the page using Google Chrome, so I wondered if I should check it in other browsers. I loaded up Firefox 3 and got the dreaded java.lang.OutOfMemoryError: Java heap space error. Tried reloading it in Chrome and now got the heap space error as well... did I flood the memory running the test, or did Firefox handle something differently?
I'm confused, as the original message cited the browser as the cause, and when I switched browsers the error changed.