Give a tip


MX Master
  • Posts

  • Joined

  • Last visited

  • Days Won


 Content Type 



Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Release Note6

Posts posted by 7twenty

  1. Amazing logic, browser crashing = skin's faultAnd it seems perfectly valid logic as well. I tested using my modded skin (based on the default one) and one of the Nitro mods, even after moving a tab back and forth 10+ times nothing happened. I then changed to the Snapper skin that's being used and BAM!! crash on the first move to the other page. The same test was repeated a number of times after changing skins/closing MX - and each and every time the same thing happened.

    The request was simply a means to check to see if the skin was in any way related to MX crashing, and from my testing it seems it is. Surely if it's a bug then it should happen on all skins?

    I understand what you're getting at, ultimately it's Maxthon that is crashing, but the point is there is something with that skin that is causing MX to crash. The fact that the feature works fine with the default skin points to something within that particular skin.

    Still waiting to see what the OP has to say if he tested the same. If he gets the same problem using a different skin, then it's possibly related to the install?

    it is not the skin i have it also here Using the default skin?

  2. Some extensions don't show icons in the toolbar or sidebar. This is especially the case for those that are made to be "always on". Normally if the extension requires or offers the user to enable/disable it, then it will be shown.

    To check that it is installed and running open the extension manager by going to the Main Menu > Extensions, or from the context menu on the Sidebar as Snero described.

  3. The CPU on 720p was ~70-90% (but played without stutter); the CPU on 1080p was high 90s to 100% and stuttered badly.

    In contrast to last night when I watched a downloaded .MKV movie (H.264) in 720p and it used ~20%A lot will depend on the codec it's encoded with. Some of the older ones aren't as efficient in the encoding process so are therefore easier to decode leading to lower CPU usage. Also many of the older codecs have at least some degree of HW acceleration via CPU/GPU. The newer codecs are even better at creating better looking and smaller files, but in turn make the CPU/GPU work harder. Some of the newer codecs may not have full HW acceleration, almost certainly not on older hardware. That would be why some are showing very low/very high. If you want to truly test different resolutions you need to ensure that they're all encoded in the same format.

    ... which reads -41 CThat's a little odd. I'm not sure if it will cause issues though, could just be an anomalie. The 83C on the other hand is a little concerning. From what i've been reading the max temp for that particular chip is approx 75-80C (i'm guessing there's some leeway), but you're right up there. If for what ever reason the CPU is overheating it could be throttling itself back to ensure it doesn't fry itself, which in turn leads to a slower CPU which leads to higher usage meaning stutter etc. Doesn't lead us to the cause, but I think the high CPU temp/usage is definitely a concern. It might just be a case of the heatsink needing to be reseated, or something else entirely.

    Will be interesting to see what you come up with (if anything) after doing the hardware disabling tests.

    At the end of the day it could just be that the system just isn't able to handle certain new codecs very well. I'll have a search and see if I can dig up any info & comparisons.

  4. I just tested again on a new portable install and also with a passport account, and it worked fine in both cases. I can't see any reason why it isn't working for you. I have not tested with the installer version, but I can't see any reason why that would be different as it's basically the same files packaged differently and set to use the %appdata% folder to save userdata.

    Did you remove the HOSTS file workaround by any chance? If I recall correctly it's still required. So the file workaround might be working, but you are actually seeing the suggestions provided by api.bing.com.

  5. Is that using Flash?Yes, I always use flash unless forced to use HTML5. MX popout video is too handy.

    Hmph, yeah I know. I'm trying to avoid that 'cos, apart from being time-consuming, I've never done it before and I don't know how aggressive to be in disabling stuff - there's a lot of stuff.I made a quick reference for you to use. Anything marked orange you can disable without issue (apart from the last one), every section also has a comment. There's some sections where you probably could try disabling more, but probably not worth it especially if you're a little hesitant. But if you're unsure on what it does or if it's connected to something else (like the mouse) don't disable it. Hopefully that'll be enough to get an answer.


  6. AylaAsperger replied at 2014-11-30 04:14 back.gif

    Yes I found it, I was looking in program files when I posted that and it's in appdata. But it didn't work!Are you following the instructions correctly? I've been using this workaround since I found it while using and have since updated to .3000 and it still works fine.

    Empty text file named to update.db, marked as read-only in the public\smarturl folder.


    Also interesting that no rep has made any mention about the porn links suggestions?

  7. Have you run Maxthon at least once so the files are updated? The userdata folder isn't created until MX is run the first time. And are you looking in the right place?

    It should be in the UserData\public\SmartUrl folder. If you used the installed version of Maxthon, open an explorer window and paste in %appdata%\Maxthon3\UserData\Public\SmartUrl in the address bar. For the portable version, userdata is in the folder Maxthon was extracted to.

  8. I just tested MX4 on a Windows 8.1 tablet with a dual core 1.33Ghz Atom processor, when running a video as described above CPU usage was between 20-30%, though it did max out at certain times, but I think that was due to me switching apps a lot. The default metro player played them 5-10%. MX is clearly not as optimised as other players or it's a HWA issue.

    Even on my desktop system Maxthon uses 5-10% more than Chrome which hovers ~5%, and that's an i5 3.3Ghz.

    Are you sure the CPU is running at full speed and not being artificially restricted somehow, or being throttled down due to heat issues? Use HWMonitor to check your temps and CPU-Z to check CPU speeds.

    On your F:\ drive install, did you try downloading with MX and check it's cpu usage?

    I think going back and doing this test might be best:

    2. Go to Device Manager, disable all devices that aren't required (so anything apart from display, graphics card, main HDD, keyboard, mouse etc) Disable everything else (right-click, disable) restart and do the copy tests again. If the problem doesn't happen after disabling everything, then we know it's a device/driver issue. From then you enable one device at a time and test. Keep doing this until it starts happening again.

  9. Same here. I think it's almost certainly to do with AdHunter. For me at least, it runs in Flash with Ultra, and HTML5 in Retro. If you turn off AH they both start instantly (although with ads). AH just might work better with HTML5. When the adblock extension that was announced finally happens things might change.

    Until then the other option and probably the best one, is to use the Youtube Centre extension. I'm not one for adding plenty of extensions to the browser, but this is by far one of the best, adding lots of options, removes ads perfectly and is also constantly being updated.

  10. Before you get too far along with that, test with a local file using maxthon's native playback, just drag a file onto Maxthon. This should isolate anything related to network hardware/drivers being the issue, if that works with normal CPU usage then the problem isn't with mx or it's playback capabilities. It also leads us back to it being a hardware or driver issue almost certainly related to networking. Or flash being the culprit. At least that's the idea.

    EDIT: it can't be hardware related as your other install works fine, so driver issue is where we're at I think.

  11. How is Maxthon Passport relevant? O_oIt's just a means of testing to see if it's related to your userdata files in case there is an issue in there somewhere.

    If that doesn't work then it could be something in the public folders which are global settings. Best way to test that is downloading the portable version and testing with that.

    So if it works fine signed out then it's a userdata issue, if it works fine with the portable version then it's most likely one of the public settings that's gone awry.

    You could also just reinstall Maxthon as noted by the poster above, or just restore the spellcheck files from here. I usually work by trying to find the cause of the issue, then resolve it. This way I can say for sure that it was due to a faulty file/setting etc.

  12. In case it's a settings related issue with Maxthon, you can just download/extract/run the portable version of Maxthon. It won't have any of your settings (unless you sign in, which you shouldn't for testing purposes). That way you can be certain it's not something you changed within Maxthon. Still doesn't rule MX out, but I think we're at the point where it's pretty evident it isn't the cause.

    RE: the flash issue. As you found out, MX installs it's own flash and also can be removed by renaming the file. If you installed another version of Flash you need to ensure it's the correct one. IE has it's own one, as does Chrome. I had this very issue when I recently re-installed Windows. You need to install the NPAPI (for firefox) version (not sure if the wording is the same for older versions). If it installs correctly and is the right one, and the file in the Maxthon folder is renamed/deleted then MX will use the installed NPAPI version on the system.

    RE: the temp files, I don't think that's an issue, apparently the "C:\$ConvertToNonresident" is an NTFS thing that occurs internally when doing some file copy operations. MX might cause some extra copy operations due to the way the temp files are accessed/stored, but as you saw earlier, copying files doesn't add that much load to the system.