504 Gateway timeout

    Could be based on memory or something you have installed. I only have 4 gig here and might be why FF crashed because not enough free system memory to cope with it.

    I did have DivX running in background converting a movie when I clicked the link before, that takes up a fair bit of CPU processing.

    Edited once, last by NicoleSophie (November 8, 2016 at 4:12 PM).

    2.9 GHz (quads core)

    8 GB ram

    1 GB video

    0 plugins

    0 extensions

    It crashed for me and everyone else I showed it too (just not a few people here). It also could be reproduced by the staff, which is why they kept deleting a few of my examples (that were more intense).

    How or why really is no longer important. This appears to be fixed in the trunk (development) branch of the software. I'll check again for beta 5 and all the way through to release, to make sure this does not reoccur.

    But let's more on... The important matter is that it was fixed and not ignored.

    System

    Windows 10 Enterprise 2016 LTSB (1607.14393.447) - 64bit

    Windows 7 Enterprise (6.1 build 7601 : Service Pack 1) - 64bit

    Windows XP Professional (5.1 build 2600.xpsp_sp3_qfe.161003-1531 : Service Pack 3) - 32bit

    VOJ320F1A on NVIDIA GeForce GT 430 (1GB DDR3)

    Screen Resolution:1920px x 1080px

    AMD Athlon II X4 630 (2.8 Ghz)

    8.00GB Dual-Channel DDR3 Ram

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login