View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
3091 | Composr | installer | public | 2017-02-24 12:29 | 2017-03-06 20:35 |
Reporter | Adam Edington | Assigned To | Chris Graham | ||
Priority | normal | Severity | trivial | ||
Status | resolved | Resolution | fixed | ||
Summary | 3091: White screen on Step 6 | ||||
Description | When trying to install the forum it often just offers a white screen on Windows 10 (2 different PC's gave the same result). It eventually latches on if you hit the back button and let it auto-proceed, though it takes a few tries. | ||||
Tags | No tags attached. | ||||
Attach Tags | |||||
Time estimation (hours) | |||||
Sponsorship open | |||||
|
I've roughly halved the number of database queries used, I think this will solve it. |
|
Same issue on RC33 and I wouldn't consider my disk slow (though the installer does skip file checking because it thinks it is). It's like there is no attempt to initatiate the data transfer by the browser (Firefox) on Step 6. Takes a few tries for it to do so. |
|
:( Is it an SSD or a traditional magnetic HDD? I've observed many times Windows is much slower accessing small files that Linux, I'm not sure if that's a disk caching thing or something to do with how NTFS works. How long until it white screens in seconds? |
|
It's a standard HDD but ocportal and early RC's didn't consider the disk slow. It pretty much white screens as soon as the Step 5 autoproceed counter ends. I have to hit back and let it try again until it takes. Once it does it takes a few seconds to complete the actual step. |
|
I just tested on WAMP running on a VM of Windows 10 and it went through okay. |
|
Okay, perhaps it's a Bitnami Wampstack thing or my machine, though this a new PC with twice the amount of everything my old one had so strange to be encountering the same issues I had on the old machine. If nobody else is having this issue, I guess I can live with it as it eventually works. |
|
Now fixed. Bitnami set a Zend OpCache extension setting unusually high opcache.revalidate_freq=60 This broke the config file loading within the installer. It was initially blank, Composr would load it for default settings, Zend OpCache cached it as blank, Composr wrote the file, but it would take 60 seconds before it would decache so the next screen (when it was needed) failed due to the stale cached blank version. |
|
Ahh right, glad you tracked it down and fixed :) |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-02-24 12:29 | Adam Edington | New Issue | |
2017-02-26 23:11 | Chris Graham | Note Added: 0004818 | |
2017-02-26 23:11 | Chris Graham | Status | Not Assigned => Resolved |
2017-02-26 23:11 | Chris Graham | Resolution | open => fixed |
2017-02-26 23:11 | Chris Graham | Assigned To | => Chris Graham |
2017-03-03 13:14 | Adam Edington | Note Added: 0004831 | |
2017-03-03 13:16 | Adam Edington | Note Edited: 0004831 | |
2017-03-03 13:17 | Adam Edington | Note Edited: 0004831 | |
2017-03-03 15:24 | Chris Graham | Note Added: 0004832 | |
2017-03-03 15:32 | Adam Edington | Note Added: 0004833 | |
2017-03-03 17:35 | Chris Graham | Note Added: 0004839 | |
2017-03-06 10:39 | Adam Edington | Note Added: 0004849 | |
2017-03-06 19:01 | Chris Graham | Note Added: 0004850 | |
2017-03-06 20:35 | Adam Edington | Note Added: 0004852 |