• 0

    posted a message on Addon causing memory allocation error: block too big
    ok, did some testing in raid and with cowtip's border set to default - no problem, memory increases but only due to recount and not by excessive amounts - dump and recount clear takes it back down.

    With border set to Caith2 (added through SharedMedia) the memory gets crazy, and dump/clearing recount doesn't take it anywhere near initial - 20/30mb off.

    So i've no clue what that means, but I guess I will just stick to default tooltip appearance (unless I bother replacing the default tooltip in interface folder, which is what my old UI did and that worked).
    Posted in: AddOn HELP!
  • 0

    posted a message on Addon causing memory allocation error: block too big
    Quote from Dridzt
    Did you maybe find an interesting (and complex) tag that you applied to Cowtip in between though?

    (between the time you were using it pre-3.0 and after you rebuilt your ui)


    Defaults both before and after.


    Will probably just see how tonight goes for now, though will probably install startip regardless, all I want a tooltip mod for is reposition(mainly) and skinning(secondly).
    Posted in: AddOn HELP!
  • 0

    posted a message on Addon causing memory allocation error: block too big
    Quote from yssaril
    disabling cowtip might solve the issue for you but cowtip is probably not the only cause for it its proabbly one of several addons that you use that contribute to it and cowtip just happens to be blamed for it

    i have used cowtip for for hours on end (raiding/pvping) and never had a problem


    As have I with pretty much all of my current addons installed too, which is why this is extra annoying.


    As a matter of interest, anyone know what "usual memory usage" should look like? yesterday every wipe (wiping after 3.0, really what were we playing at?) memory usage was up 5mb from the time before (after resetting recount). Should it be going up by more than an MB or 2?
    Posted in: AddOn HELP!
  • 0

    posted a message on Addon causing memory allocation error: block too big
    Quote from honem
    OP I can remember a thread from 3 months ago about CowTip causing memory problems. So no it didn't just come along with 3.0


    I saw that but was confused as I've been using 90% of the mods of I have now, cowtip included, for a year without problems :(

    Plan for tonight is I deleted cowtip and its settings and reinstalled it and m8 with my UI is going to disable cowtip to 1. see if it is cowtip, 2. see if its fixed by an easy reinstall (bit of wishful thinking I know!)
    Posted in: AddOn HELP!
  • 0

    posted a message on problem with casting "locking up"
    sounds like the problem I am having (apparantly the likely culprit is cowtip, do you use it?)

    http://forums.wowace.com/showthread.php?p=246369#post246369
    Posted in: AddOn HELP!
  • 0

    posted a message on Addon causing memory allocation error: block too big
    Quote from Dridzt
    I think you're in denial a bit mate :)

    1. Other reports tend to indicate that Cowtip exacerbates the problem
    (if not causing it, as no one has verified that it does or does not sofar)
    2. It is the first addon mentioned in the error log you posted.
    3. How about disabling it for your next couple raids and see if you don't have the problem?

    I also haven't seen a mention of this error yet that didn't have to do with an excessive amount or very deep nested frame structures created.
    'SetRegions' features in error reports related to it predominantly...

    I don't see where Recount fits into that.

    Edit: was replying to the OP (not the post that came in between)


    Will probably run without cowtip in tomorrows raid and have my m8 run with it but without recount, or visa versa, and have a looksie at memory usage.

    I don't see why it would cause a problem now and not before (cowtip or recount) - obviously 3.0 can and did break addons but if it were a common problem I would have imagined there would be threads about this already. The only thing thats changed in my setup of either of these mods is previously cowtip's borders were just blizzard tooltip borders that were replaced with a custom one in the interface/tooltips folder whereas now they are added through sharedmedia. Only reason I mention this is "somewhere" I saw it mentioned that images weren't garbage dumped (i think). Also on thursday when i raided before the problem started cowtip was broken and just had default appearance (appearance settings were gone).

    Any reason cowtip (if its that) might only be a problem in raids?



    Oh - and thanks for the suggestions so far, I would be happy to at least pin it to a mod even if I can't fix it.
    Posted in: AddOn HELP!
  • 0

    posted a message on Addon causing memory allocation error: block too big
    Since Friday/Saturday I've been receiving "Memory Allocation Error: Block too big" during prolonged raiding (1-3 hours).

    I nuked my UI in 3.0 and started rebuilding it, though unfortunatly I wasn't able to find updated mods for everything so in places I am running out of date mods. I raided on thursday without a problem and first noticed this problem yesterday (Saturday) and again today.

    I'm on Vista and have the Curse client auto updating addons.

    As I'm sure most of you are aware, this problem consists of what can only be called an entire UI break down - mods that are already open continue to work - sort of (i.e. I can click on grid for example, but my quartz cast bar will cease to work and just gets locked at whatever it was doing when the error occured).

    I've been reading up as much as I can about what may be the cause, checking pages and forum threads relating to mods - I came across a forum thread or two on the official forums that basically pointed the finger at cowtip but I've been using cowtip for a year without a problem (though I nuked my UI I did reinstall many of the same mods and basically rebuilt it so it looked the same). The thing I find most off putting is that I can't find anyone else still experiencing this problem except a guildie thats using my UI.

    A few screenies:

    bugsack open just after errors occured:
    http://img529.imageshack.us/my.php?image=wowscrnshot101908210405tk3.jpg


    Performancefu showing the memory hogging isn't being attributed to anything:
    http://img530.imageshack.us/my.php?image=wowscrnshot101908210604nk7.jpg

    Screeny of addons folder:
    http://img183.imageshack.us/my.php?image=mymodsje5.jpg


    So my question is - does anyone know which mods are likely / known to still be causing the problem? If so is it something that can be fixed the threads I was reading made it sound like there wasn't a fix as it was just the way the game was (which as I say seems odd as I have been using most of these mods for a year).

    Thanks in advance.
    Posted in: AddOn HELP!
  • 0

    posted a message on Omen - Bug Reports and Suggestions
    im also having the problem with the anchor going central instead of top/bottom, currently on revision 68842 - I update all my mods about once a day - had this problem since 2.4 came out.

    If it makes a difference, i've got auto collapse on but grow up off.

    When I unlock and drag it into place it seems to work for the duration of my login, however after I relog the anchor is back central.

    I don't suppose it will make a difference, but I also have title and module bar hidden.
    Posted in: Raid AddOns
  • To post a comment, please or register a new account.