Opened 49 minutes ago
Last modified 38 minutes ago
#539 new defect
OpenLayers map on homepage may appear blank on new install
| Reported by: | Jeff McKenna | Owned by: | Jeff McKenna |
|---|---|---|---|
| Priority: | critical | Milestone: | 5.2.1 release |
| Component: | MS4W - Base | Version: | 5.2.0 |
| Keywords: | Cc: | TC Haddad | |
| Blocked By: | Blocking: |
Description (last modified by )
- initially reported by @tchaddad
- honestly I once saw this happen during the 5.2.0 release candidate process
- in my case, it only happened on my heavily used machine, with tons of tabs open, in Firefox (that was running a long time, weeks likely, without an update)
- by "heavily used" I mean I was running the setup.exe installer over and over again into different ports and folders and tabs, and eventually one run caused a blank map in the OpenLayers map on MS4W's homepage (127.0.0.1)
- clearing the browser cache didn't fix it
- magically, I closed Firefox (hard restarted it) and I have never seen this issue since
- in my case, it only happened on my heavily used machine, with tons of tabs open, in Firefox (that was running a long time, weeks likely, without an update)
Needs more research (and hopefully steps to replicate here). From quick research I notice other OpenLayers users with somewhat similar reports:
This will be a tough one. Hmm. Any more findings @tchaddad??
Seems like some sort of memory issue.
Difficult to know yet if a change is needed inside the actual MapServer source code, or to MS4W's embedded OpenLayers code.
Change History (5)
comment:1 by , 48 minutes ago
| Description: | modified (diff) |
|---|
comment:2 by , 47 minutes ago
| Description: | modified (diff) |
|---|
comment:3 by , 45 minutes ago
| Summary: | OpenLayers map on homepage may appear blank on first load → OpenLayers map on homepage may appear blank on new install |
|---|
comment:4 by , 44 minutes ago
| Description: | modified (diff) |
|---|
comment:5 by , 38 minutes ago
Note:
See TracTickets
for help on using tickets.

Oh also, back when it happened, I remember checking and the embedded OpenLayers code wasn't even being called by the browser (and that absolutely confused me).
Eventually I tried a browser restart and have never hit that issue since.