Ouch ! (Seattle 10.0) ... when I hit the "Close program" button, Delphi dies in terrible pain saying "Exception: EConvertError in rtl230.bpl at 0011F067, no argument for format 'docwiki.embarcedro.com/RADtud.' and 'Exception: EOSError in rtl230.bok at 0004DC21, System code 5- Access denied'

-

Ouch ! (Seattle 10.0) ... when I hit the "Close program" button, Delphi dies in terrible pain saying "Exception: EConvertError in rtl230.bpl at 0011F067, no argument for format 'docwiki.embarcedro.com/RADtud.' and 'Exception: EOSError in rtl230.bok at 0004DC21, System code 5- Access denied'

Comments

  1. Marco CantùNovember 24, 2015 at 7:48 AM

    With or without Update 1? Worth reporting, and listing any add-on you have. Even if it might be a bit elusive...

    ReplyDelete
  2. Paul TOTHNovember 24, 2015 at 7:52 AM

    10.0  for no update.

    but it's a known bug RSP-12975

    ReplyDelete
  3. David MillingtonNovember 24, 2015 at 10:18 AM

    A link is better, people can vote :) https://quality.embarcadero.com/browse/RSP-12975

    One of the duplicates seems to indicate it's a problem with the French language pack.

    ReplyDelete
  4. Graeme GeldenhuysNovember 24, 2015 at 4:28 PM

    Is it just my imagination or is Seattle 10 very prone to IDE crashing? I've seen more reports than usual.

    ReplyDelete
  5. Lars FosdalNovember 24, 2015 at 11:12 PM

    I have the opposite observation. XE7 had to be restarted many times a day. #10Seattle lasts all day. I use very few add-ons, except those from David Millington​ :)

    ReplyDelete
  6. Paul TOTHNovember 25, 2015 at 12:13 AM

    I daily use XE3 and Seattle, Seattle is much better :) 

    I sometime still use D6 for an old project, a real pleasure ;)

    ReplyDelete
  7. Graeme GeldenhuysNovember 25, 2015 at 1:19 AM

    Either way, I still see an alarming amount of #Seattle10 crash reports being mentioned all over the Internet. Wow, so if you guys say Seattle is much better, that means earlier XE versions were pretty damn bad. :-/

    I still maintain D7 projects for clients and hardly see any crashes - maybe one a week or so. I also use Lazarus and MSEide (both Object Pascal language IDE's) for the most part of my day-to-day work, and they never crash. Come on EMBT, open-source software is outshining you at every turn, and they have a fraction of resources you do. If you want to charge that much for a product, make sure it's a descent [maybe even high] quality product.

    ReplyDelete
  8. Lars FosdalNovember 25, 2015 at 1:25 AM

    Graeme Geldenhuys - "an alarming amount of #Seattle10 crash reports being mentioned all over the Internet." - That's FUD.

    ReplyDelete
  9. Paul TOTHNovember 25, 2015 at 1:25 AM

    I think that the top 3 points that have to be fixed (for the IDE part) are:
    - Free method not found in class TList (!!!!!)
    - IDE freeze while deploying Android/iOS application (have you heard about threads ?)
    - better error reporting for mobile development, especially when deployment fails

    ReplyDelete
  10. Lars FosdalNovember 25, 2015 at 1:39 AM

    Paul TOTH The "Free method not found" - That's Error Insight "does not contain a member named Free", right?  

    Happens for a lot of classes and for other methods.
    - does not contain a member named 'ClassName' / 'QualifiedClassName' / 'ClassType' / 'GetHashCode'

    All of these are in TObject - but TObject has TWO public sections - can it be that Error Insight discards those methods that are in the first public section - once the second public section is detected?

    Another issue is helper methods 
    - 'NativeInt' does not contain a member named 'ToString' .

    Error Insight has a lot of issues.  Warnings for missing overload statement for constructors - in the implementation section is another issue.

    ReplyDelete
  11. Paul TOTHNovember 25, 2015 at 1:58 AM

    Lars Fosdal yes i'm talking about that, and it's the first thing a new Delphi developer sees, the first thing I have to talk about in a formation :/

    ReplyDelete
  12. Lars FosdalNovember 25, 2015 at 4:55 AM

    After having another look, I don't think it is the second public section anymore, but rather the conditional defines in the declarations that throws Error Insight off.

    ReplyDelete

Post a Comment